CVE-2025-67635 is a high-severity (CVSS 7.5) CWE-404 vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.
Jenkins has a Denial of service vulnerability in HTTP-based CLI
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67635.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-67635 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:cli☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:cliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.529&&< 2.541 | 2.541org.jenkins-ci.main:jenkins-core:2.541 |
| ☕Maven | org.jenkins-ci.main:cli | ≥ 2.529&&< 2.541 | 2.541org.jenkins-ci.main:cli:2.541 |
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.528.3org.jenkins-ci.main:jenkins-core:2.528.3 |
| ☕Maven | org.jenkins-ci.main:cli | all versions | 2.528.3org.jenkins-ci.main:cli:2.528.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.541 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67635 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-67635 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-67635. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| OpenShift Developer Tools and Services 4.12 | ocp-tools-4/jenkins-rhel8:v4.12.0-1765819949 | RHSA-2025:23487 |
| OpenShift Developer Tools and Services 4.13 | ocp-tools-4/jenkins-rhel8:v4.13.0-1765819949 | RHSA-2025:23482 |
| OpenShift Developer Tools and Services 4.14 | ocp-tools-4/jenkins-rhel8:v4.14.0-1765820005 | RHSA-2025:23485 |
| OpenShift Developer Tools and Services 4.15 | ocp-tools-4/jenkins-rhel8:v4.15.0-1765820005 | RHSA-2025:23486 |
| OpenShift Developer Tools and Services 4.16 | ocp-tools-4/jenkins-rhel9:v4.16.0-1765868606 | RHSA-2025:23490 |
| OpenShift Developer Tools and Services 4.17 | ocp-tools-4/jenkins-rhel9:v4.17.0-1765868606 | RHSA-2025:23489 |
| OpenShift Developer Tools and Services 4.18 | ocp-tools-4/jenkins-rhel9:v4.18.0-1765868606 | RHSA-2025:23492 |
| OpenShift Developer Tools and Services 4.19 | ocp-tools-4/jenkins-rhel9:v4.19.0-1765868606 | RHSA-2025:23488 |
Frequently Asked Questions
Is CVE-2025-67635 in your dependencies?
O3 Security finds CVE-2025-67635 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.