7.5
High
org.jenkins-ci.main:jenkins-core

CVE-2026-33002

CVE-2026-33002 is a high-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 2.442, < 2.555. It is fixed in 2.555.

Key facts
CVSS score
7.5
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
org.jenkins-ci.main:jenkins-core
Fixed in
2.555
Disclosed
2026

Summary

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.

Impact

Severity and exposure

CVE-2026-33002 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.555). Upgrading removes the vulnerable code path.

Affected versions

maven

  • org.jenkins-ci.main:jenkins-core (>= 2.442, < 2.555)

Security releases

  • org.jenkins-ci.main:jenkins-core → 2.555 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-33002 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-33002 is reachable in your applications. Get a demo

Remediation advice

Upgrade org.jenkins-ci.main:jenkins-core to 2.555 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-33002

What is CVE-2026-33002?

CVE-2026-33002 is a high-severity security vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions >= 2.442, < 2.555. It is fixed in 2.555.

How severe is CVE-2026-33002?

CVE-2026-33002 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2026-33002?

org.jenkins-ci.main:jenkins-core (maven) versions >= 2.442, < 2.555 is affected.

Is there a fix for CVE-2026-33002?

Yes. CVE-2026-33002 is fixed in 2.555. Upgrade to this version or later.

Is CVE-2026-33002 exploitable, and should I be worried?

Whether CVE-2026-33002 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-33002 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-33002?

Upgrade org.jenkins-ci.main:jenkins-core to 2.555 or later.

Stop the waste.
Protect your environment with Kodem.