High-Severity Jenkins Vulnerability Allows Unauthenticated DoS via HTTP CLI
Jenkins has released patches to address a significant denial-of-service (DoS) vulnerability affecting numerous organizations utilizing its automation server for continuous integration and deployment pipelines. The vulnerability is present in Jenkins…
Jenkins has released patches to address a significant denial-of-service (DoS) vulnerability affecting numerous organizations utilizing its automation server for continuous integration and deployment pipelines. The vulnerability is present in Jenkins versions 2.540 and earlier (LTS 2.528.2 and earlier) and allows unauthenticated attackers to initiate DoS attacks through the HTTP-based command-line interface.
The issue arises from improper connection handling when HTTP CLI streams are corrupted, enabling malicious actors to deplete server resources without authentication. This flaw is due to Jenkins's connection management logic failing to properly terminate corrupted connections.
Attribute Value
CVE ID CVE-2025-67635
Vendor / Project Jenkins
Vulnerability Type Denial of Service (DoS) via HTTP-based CLI
This flaw is due to Jenkins's connection management logic failing to properly terminate corrupted connections.
CVSS Base Score High
CVSS Vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector Network (HTTP-based CLI)
Description Improper closing of corrupted HTTP-based CLI connections allows unauthenticated DoS by exhausting threads.
This vulnerability permits attackers to send specially crafted connection requests that cause request-handling threads to hang indefinitely, effectively freezing resources and hindering legitimate traffic processing. The vulnerability can be exploited remotely without authentication over the network, posing an immediate risk to Jenkins installations exposed to untrusted networks or the public internet.
Organizations are advised to upgrade to Jenkins 2.541 or LTS 2.528.3, which include patches for properly closing HTTP-based CLI connections when stream corruption occurs. These updates restore normal resource cleanup and prevent thread exhaustion attacks.
It is recommended that security teams prioritize patching all Jenkins deployments, especially those facing the internet. Monitoring systems for unusual connection patterns or thread count anomalies that might indicate exploitation attempts is also advised.
Based on reporting by Cyber Security News.
