dbcve.org
JenkinsApplication

CVE-2026-33002

HIGH · 7.5 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 2.541.3 / 2.555 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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.442 through 2.554 (both inclusive), LTS 2.426.3 through LTS 2.541.2 (both inclusive) performs origin validation of requests made through the CLI WebSocket endpoint by computing the expected origin for comparison using the Host or X-Forwarded-Host HTTP request headers, making it vulnerable to DNS rebinding attacks that allow bypassing origin validation.

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 fails to properly validate origins of WebSocket requests in its CLI endpoint. The application computes expected origins using Host or X-Forwarded-Host HTTP headers, which can be manipulated through DNS rebinding attacks to bypass origin validation checks, allowing attackers to impersonate legitimate origins.

MitigationUpgrade Jenkins to version 2.555 or later (weekly) or LTS 2.541.3 or later. If upgrading is not immediately possible, disable the CLI WebSocket endpoint or implement network-level controls to prevent DNS rebinding attacks.

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.426.3, < 2.541.3>= 2.442, < 2.555

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or run 'java -jar jenkins.war --version' if running from WAR file, or check via CLI: 'java -jar jenkins-cli.jar -s http://localhost:8080 who-am-i' (requires authentication)
    Affected if Version is 2.426.3 <= installed version < 2.541.3 OR 2.442 <= installed version < 2.555 (note: 2.541.3+ and 2.555+ are fixed)
  2. Verify CLI WebSocket endpoint is enabled
    Check Jenkins configuration files for CLI WebSocket settings, or inspect network listeners. The endpoint is typically at /cli websocket path. Check in Manage Jenkins > Security > CLI or review jenkins.xml and jenkins.model.Jenkins.xml configuration files.
    Affected if CLI WebSocket endpoint is enabled and accessible (this is required for the attack vector)
  3. Check if reverse proxy headers are used
    Inspect HTTP server configuration (nginx, Apache, HAProxy, etc.) in front of Jenkins. Look for X-Forwarded-Host header handling, and check if Jenkins is configured to trust reverse proxy headers via Jenkins > Manage Jenkins > Security > Prevent reverse proxy tampering or similar settings.
    Affected if X-Forwarded-Host header is used and trusted by Jenkins without strict validation, allowing header manipulation for DNS rebinding

User is affected if running a vulnerable Jenkins version (2.426.3 to 2.541.2 or 2.442 to 2.554.x) with the CLI WebSocket endpoint enabled and configured to trust manipulable HTTP headers.

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.541.3 / 2.555 or later
Fixed in 2.541.32.555
Interim mitigation

Upgrade Jenkins to version 2.555 or later (weekly) or LTS 2.541.3 or later. If upgrading is not immediately possible, disable the CLI WebSocket endpoint or implement network-level controls to prevent DNS rebinding attacks.

Recommended fix High confidence

Jenkins 2.541.3+ (LTS) or Jenkins 2.555+ (weekly)

  1. Identify the current Jenkins version by checking the Jenkins dashboard or system information
  2. For Jenkins LTS users: Upgrade to Jenkins 2.541.3 or later (LTS 2.541.x)
  3. For Jenkins weekly users: Upgrade to Jenkins 2.555 or later
  4. After upgrade, verify the CLI WebSocket endpoint is functioning correctly
  5. Review Jenkins logs for any errors following the upgrade
Caveat Review Jenkins LTS upgrade guide for any configuration or plugin compatibility changes before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33002 — 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-2026-33002 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