How severe is CVE-2026-33001?

CVE-2026-33001 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-33001?

CVE-2026-33001 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-33001?

Update org.jenkins-ci.main:jenkins-core to 2.555 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33001 is resolved across your whole dependency graph.

How do I detect CVE-2026-33001 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-33001 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-33001 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-33001 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-33001?

CVE-2026-33001 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-33001?

CVE-2026-33001 is classified as CWE-59 (CWE-59), Path Traversal (CWE-22). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-33001 published, and has it been updated?

CVE-2026-33001 was published on March 18, 2026 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-33001 — jenkins-core

HIGHFix: jenkinsci/jenkins@6dc9993

CVE-2026-33001 is a high-severity (CVSS 8.8) CWE-59 vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Jenkins has a link following vulnerability allows arbitrary file creation

Also known asBIT-jenkins-2026-33001GHSA-r6qv-frpc-q66c

Published

Mar 18, 2026

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33001.

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.main:jenkins-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins 2.554 and earlier, LTS 2.541.2 and earlier does not safely handle symbolic links during the extraction of .tar and .tar.gz archives, allowing crafted archives to write files to arbitrary locations on the filesystem, restricted only by file system access permissions of the user running Jenkins. This can be exploited to deploy malicious scripts or plugins on the controller by attackers with Item/Configure permission, or able to control agent processes.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.555`org.jenkins-ci.main:jenkins-core:2.555`

Affected Products

1 product · 2 configurations

Application

jenkinsjenkins

< 2.555

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.555 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33001 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
OpenShift Developer Tools and Services 4.12	`ocp-tools-4/jenkins-rhel8:1776764096`	RHSA-2026:10209
OpenShift Developer Tools and Services 4.13	`ocp-tools-4/jenkins-rhel8:1776764096`	RHSA-2026:10201
OpenShift Developer Tools and Services 4.14	`ocp-tools-4/jenkins-rhel8:1776762347`	RHSA-2026:10211
OpenShift Developer Tools and Services 4.15	`ocp-tools-4/jenkins-rhel8:1776762347`	RHSA-2026:10204
OpenShift Developer Tools and Services 4.16	`ocp-tools-4/jenkins-rhel9:1776944215`	RHSA-2026:10214
OpenShift Developer Tools and Services 4.17	`ocp-tools-4/jenkins-rhel9:1776944215`	RHSA-2026:10213
OpenShift Developer Tools and Services 4.18	`ocp-tools-4/jenkins-rhel9:1776944215`	RHSA-2026:10215
OpenShift Developer Tools and Services 4.19	`ocp-tools-4/jenkins-rhel9:1776944215`	RHSA-2026:10206

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-33001 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works