dbcve.org
JenkinsApplication

CVE-2025-67635

HIGH · 7.5 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 2.528.3 / 2.541 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins does not properly close HTTP-based CLI connections when the connection stream becomes corrupted. This improper resource cleanup allows unauthenticated attackers to exhaust server resources and cause a denial of service.

MitigationUpgrade Jenkins to a version beyond 2.540 (for weekly releases) or LTS 2.528.2 (for LTS releases) to obtain the patch that properly closes corrupted CLI connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 2.528.3< 2.541

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Jenkins version
    Log into the Jenkins web UI and view the version number at the bottom of any page, or run: java -jar jenkins-cli.jar -s http://localhost:8080/ version
    Affected if The installed version is less than 2.528.3 for LTS releases, or less than 2.541 for weekly releases. Compare your version to these thresholds.
  2. Verify CLI is enabled
    Navigate to Manage Jenkins > CLI or check the system configuration. In the web UI, go to Manage Jenkins > Configure Global Security and look for CLI settings.
    Affected if CLI is enabled and accessible over HTTP/HTTPS. If CLI is completely disabled, this specific attack vector does not apply.
  3. Confirm HTTP-based CLI protocol is active
    Check which CLI protocols are available. Look for JNLP, SSH, or HTTP CLI connectors in Manage Jenkins > CLI. The HTTP CLI typically runs on port 8080 or the same port as the web UI.
    Affected if HTTP-based CLI connections are allowed. The vulnerability specifically affects HTTP/HTTPS CLI connections, not JNLP or SSH CLI.
  4. Inspect active CLI connections (optional)
    Use Jenkins script console (Manage Jenkins > Script Console) to check for hung or stale CLI connections: println(Hudson.instance.cliPorts) or monitor for many TIME_WAIT connections on the CLI port.
    Affected if Multiple stale or hanging CLI connections exist, indicating potential resource exhaustion.

You are affected if your Jenkins version is below 2.528.3 (LTS) or 2.541 (weekly) AND HTTP-based CLI is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.528.3 / 2.541 or later
Fixed in 2.528.32.541
Interim mitigation

Upgrade Jenkins to a version beyond 2.540 (for weekly releases) or LTS 2.528.2 (for LTS releases) to obtain the patch that properly closes corrupted CLI connections.

Recommended fix High confidence

Jenkins LTS 2.528.3 or later (or Jenkins 2.541+)

  1. Back up Jenkins home directory ($JENKINS_HOME) and configuration files
  2. Download the target Jenkins LTS release (2.528.3) or newer from the official Jenkins repository
  3. Stop the Jenkins service before upgrading
  4. Replace the jenkins.war file with the new version
  5. Ensure proper file permissions on the new jenkins.war
  6. Start the Jenkins service
  7. Verify the upgrade by checking the Jenkins dashboard for the new version number (Jenkins 2.528.3 or later)
  8. Test critical jobs and pipelines to ensure normal operation
Caveat Review Jenkins LTS upgrade guide for potential compatibility issues with plugins and configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67635 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data