CVE-2026-33002 is a high-severity origin validation flaw in the Jenkins CLI WebSocket endpoint affecting Jenkins 2.442 through 2.554 and Jenkins LTS 2.426.3 through 2.541.2. Jenkins introduced origin validation for the CLI WebSocket endpoint to prevent cross-site WebSocket hijacking, but in affected versions it computed the expected origin using the untrusted Host or X-Forwarded-Host HTTP request headers. Because these headers can be influenced in a DNS rebinding scenario, an attacker can bypass the origin check and establish a WebSocket connection to the Jenkins CLI endpoint from an attacker-controlled web origin. The issue affects deployments where the CLI WebSocket endpoint is available, particularly common Jetty-based Jenkins deployments such as native installers, packages, Docker containers, and java -jar jenkins.war. Successful exploitation allows the attacker to interact with the Jenkins CLI as the anonymous user and execute CLI commands permitted to that security context.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.