CVE-2025-67635: High severity Jenkins Jenkins vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.main:clito a version that resolves this vulnerability.Fixed in 2.528.3 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.528.3 - Upgrade
Upgrade
maven/org.jenkins-ci.main:clito a version that resolves this vulnerability.Fixed in 2.541 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.541
Event History
Frequently Asked Questions
What is the severity of CVE-2025-67635?
CVE-2025-67635 is classified as a denial of service vulnerability that allows unauthenticated attackers to disrupt Jenkins services.
How do I fix CVE-2025-67635?
To fix CVE-2025-67635, upgrade Jenkins to version 2.541 or later, or LTS version 2.528.3 or later.
What versions are affected by CVE-2025-67635?
CVE-2025-67635 affects Jenkins versions up to 2.540 and LTS versions up to 2.528.2.
What impact does CVE-2025-67635 have on my Jenkins instance?
CVE-2025-67635 can cause a denial of service by allowing attackers to exploit corrupted HTTP-based CLI connections.
Is CVE-2025-67635 exploitable remotely?
Yes, CVE-2025-67635 can be exploited remotely due to the nature of the vulnerability allowing unauthenticated access.