# CVE-2026-33002: Jenkins has a DNS rebinding vulnerability in WebSocket CLI origin validation

> Attackers can bypass origin validation in Jenkins CLI WebSocket endpoint via DNS rebinding, allowing unauthorized access to the interface.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** BIT-jenkins-2026-33002, GHSA-phhv-63fh-rrc8, MINI-33pr-4hpj-x2mq, MINI-4gc7-qc28-ch56, MINI-hq94-j97j-rpp2, MINI-pm5j-wwrw-56wh, MINI-vq8v-68c3-4hcc, MINI-xfq3-v6mh-cfrc

## What is CVE-2026-33002?

CVE-2026-33002 is a high-severity vulnerability in Jenkins Jenkins, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

## Which versions are affected by CVE-2026-33002?

3 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core and jenkins. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.442 | 2.555 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 2.442 | 2.555 |
| `jenkins` | Bitnami | From 2.426.3 | 2.541.3, 2.555.0 |

Products: Jenkins Jenkins.

## How do I fix CVE-2026-33002?

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

## Is CVE-2026-33002 being exploited?

There is no known exploitation of CVE-2026-33002 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Jenkins

- [CVE-2024-23897](https://insights.sbomify.com/CVE-2024-23897/): Jenkins Command Line Interface (CLI) Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2018-1000861](https://insights.sbomify.com/CVE-2018-1000861/): Jenkins Stapler Web Framework Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2017-1000353](https://insights.sbomify.com/CVE-2017-1000353/): Jenkins Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-5317](https://insights.sbomify.com/CVE-2015-5317/): Jenkins User Interface (UI) Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2021-21690](https://insights.sbomify.com/CVE-2021-21690/): Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33002 and fix it if it is affected.

What it is: CVE-2026-33002 is a high-severity vulnerability in Jenkins Jenkins, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-33002 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.442; fixed in 2.555
- org.jenkins-ci.main:jenkins-core (Maven): affected from 2.442; fixed in 2.555
- jenkins (Bitnami): affected from 2.426.3; fixed in 2.541.3, 2.555.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33002/ (Markdown: https://insights.sbomify.com/CVE-2026-33002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33002
- OSV: https://osv.dev/vulnerability/CVE-2026-33002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33002/
Summaries are generated and may contain mistakes; the official description above is the record.