Widely-used Jenkins CI/CD platform; exploit could enable code execution, disrupting build pipelines across many organizations.
CVE-2026-33001
Jenkins archive extraction flaw allows arbitrary file write via symlinks.
Is CVE-2026-33001 being exploited?
Not confirmed. CVE-2026-33001 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.1% probability of exploitation in the next 30 days.
How severe is CVE-2026-33001?
CVE-2026-33001 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33001?
Yes. A fix has been recorded for CVE-2026-33001. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33001 affect?
CVE-2026-33001 affects Jenkins 2.554 and earlier, Jenkins LTS 2.541.2 and earlier. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33001?
Upgrade to fixed Jenkins version (2.555+ or latest LTS).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary file write via symlinked tar extraction; attacker with Item/Configure or agent control could trigger code execution on the Jenkins controller.
Patch when possible