CVE-2026-33002
Jenkins 2.426.3 – 2.541.3
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-33002 is a high-severity Reliance on Reverse DNS Resolution for a Security-Critical Action (CWE-350) vulnerability in Jenkins Jenkins. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-3 (Device Identification and Authentication) and SC-20 (Secure Name/Address Resolution Service (Authoritative Source)) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33002 is a vulnerability in Jenkins versions 2.442 through 2.554 (inclusive) and LTS versions 2.426.3 through 2.541.2 (inclusive) that affects origin validation for requests to the CLI WebSocket endpoint. The software computes the expected origin for comparison using the Host or X-Forwarded-Host HTTP request headers (CWE-350: Origin Validation Error), enabling DNS rebinding attacks to bypass this check. Published on 2026-03-18, it has a CVSS v3.1 base score of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
Attackers can exploit this remotely over the network without privileges, though it demands high complexity and user interaction. By leveraging DNS rebinding, they bypass origin validation on the CLI WebSocket endpoint, potentially achieving high impacts on confidentiality, integrity, and availability.
Mitigation details are outlined in the Jenkins security advisory at https://www.jenkins.io/security/advisory/2026-03-18/#SECURITY-3674.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12845
Vulnerability Data
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…
more
it vulnerable to DNS rebinding attacks that allow bypassing origin validation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requiring unique device identification and authentication before any connection prevents security decisions based solely on unverified reverse DNS lookups.
Mandating data-origin authentication for name/address resolution stops reliance on unauthenticated reverse DNS responses.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication of users/services/hardware directly prevents security decisions based on unauthenticated reverse DNS.
Monitoring DNS services can detect adverse events stemming from unverified reverse lookups.
Network protections reduce the feasibility of attackers exploiting unauthenticated reverse-DNS decisions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network security controls can enforce authenticated, non-DNS-based host identification.
Secure network services discourage use of unauthenticated reverse-DNS for access decisions.
Application security requirements can mandate authenticated host verification instead of reverse DNS.
Secure architecture principles discourage reliance on unauthenticated DNS for security decisions.
Secure coding practices can replace reverse-DNS checks with cryptographically verified identities.
Strong authentication mechanisms reduce reliance on unauthenticated DNS-based identity decisions.