CVE-2025-67635VulnerabilityPublished 10 Dec 2025Updated 16 Dec 2025

CVE-2025-67635: Jenkins · Vulnerability

Affects JenkinsSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.jenkins-ci/main`pkg:maven/org.jenkins-ci/main`Other threats	Affected <=2.540	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Jenkins to a version later than 2.540 (or LTS later than 2.528.2) as soon as official patches or releases addressing CVE-2025-67635 become available. 2. Until patches are applied, restrict network access to Jenkins HTTP-based CLI interfaces by implementing strict firewall rules, VPN access, or network segmentation to limit exposure to trusted users and systems only. 3. Disable the HTTP CLI protocol if not required, or switch to more secure communication methods such as SSH-based CLI access. 4. Monitor Jenkins server logs and network traffic for abnormal or persistent CLI connection attempts that may indicate exploitation attempts or resource exhaustion. 5. Implement resource limits and connection timeouts on Jenkins servers to mitigate the impact of hanging or corrupted connections. 6. Regularly audit Jenkins configurations and access controls to ensure minimal exposure of management interfaces. 7. Incorporate Jenkins vulnerability scanning and patch management into the organization's security operations and DevSecOps practices to ensure timely detection and remediation of such vulnerabilities.

Description

Jenkins 2.540 and earlier, LTS 2.528.2 and earlier does not properly close HTTP-based CLI connections when the connection stream becomes corrupted, allowing unauthenticated attackers to cause a denial of service.

Impact

For European organizations, the primary impact of CVE-2025-67635 is denial of service against Jenkins servers, which are critical components in modern software development and deployment workflows. Disruption of Jenkins services can halt CI/CD pipelines, delaying software releases, updates, and security patches, thereby increasing operational risk. Organizations relying on Jenkins for infrastructure automation, testing, or deployment may experience significant downtime, affecting business continuity and potentially causing financial losses. In sectors such as finance, telecommunications, manufacturing, and public services, where automation and rapid deployment are essential, this vulnerability could lead to cascading operational disruptions. Additionally, prolonged outages may increase the attack surface by forcing organizations to revert to manual processes or less secure alternatives. Since the vulnerability requires no authentication and can be exploited remotely, exposed Jenkins instances in European data centers or cloud environments are at heightened risk. The lack of confidentiality or integrity impact reduces the risk of data breaches but does not mitigate the operational consequences of service unavailability.

CWE-404Improper Resource Shutdown or Release (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not release or incorrectly releases a resource before it is made available for re-use.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error…
Implementation
Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
Attack patterns
TCP Fragmentation (opens in a new tab)
UDP Fragmentation (opens in a new tab)
ICMP Fragmentation (opens in a new tab)
BlueSmacking (opens in a new tab)
Flooding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jenkins.io/security/advisory/2025-12-10/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Dec 2025, 18:01 UTC

WeaknessesCWE-404

Technical details

References

Community reviews

Related threats