CVE-2026-33001

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.

Published: 2026-03-18 Last update: 2026-03-20 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-33001 is rated Moderate Risk (52.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.26%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-33001

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-25 0.22% 0.26% +0.04%
2 2026-05-13 0.11% 0.22% +0.12%
3 2026-03-21 0.11%

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-33001

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-33001

GitHub Security Advisory for CVE-2026-33001

GHSA-r6qv-frpc-q66c · Severity: high · Ecosystem: maven — Jenkins has a link following vulnerability allows arbitrary file creation

OS Trackers for CVE-2026-33001

vendor priority summary link
alpine CVE-2026-33001: 1 source package rows (jenkins); 22 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 22. https://security.alpinelinux.org/vuln/CVE-2026-33001
redhat high https://access.redhat.com/security/cve/CVE-2026-33001

Affected software / configurations for CVE-2026-33001

Vendor Product Version Raw CPE
jenkins jenkins < 2.541.3 cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*
jenkins jenkins < 2.555 cpe:2.3:a:jenkins:jenkins:*:*:*:*:-:*:*:*

References for CVE-2026-33001

cvelogic Threat Intelligence