dbcve.org
JenkinsApplication

CVE-2026-33001

HIGH · 8.8 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 2.541.3 / 2.555 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Jenkins fails to safely handle symbolic links when extracting .tar and .tar.gz archives, allowing path traversal that can write files to arbitrary filesystem locations restricted only by the Jenkins process user's permissions.

MitigationUpgrade Jenkins to a patched version beyond 2.554 (or LTS beyond 2.541.2) that implements safe symlink handling during archive extraction, and ensure the Jenkins process runs with minimal filesystem privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:< 2.541.3< 2.555

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or run `java -jar jenkins.war --version` from the jenkins_home directory. Alternatively, check the jenkins/model/Jenkins.java source file or the installed package version.
    Affected if The version is earlier than 2.555 for weekly releases, or earlier than 2.541.3 for LTS releases.
  2. Locate plugins or features that handle .tar or .tar.gz archive extraction
    Review the installed plugins list (Manage Jenkins > Manage Plugins > Installed) for any plugins related to archive handling, packaging, or artifact management. Check job configurations for uses of archive extraction steps.
    Affected if Plugins or job configurations that extract .tar or .tar.gz archives are present and active.
  3. Examine the Jenkins process user filesystem permissions
    Run `ls -la` on the Jenkins home directory and check which user owns the jenkins process (via `ps aux | grep jenkins`). Verify write permissions to directories outside the normal jenkins workspace.
    Affected if The Jenkins process user has write access to system directories outside the jenkins_home (e.g., /tmp, /var, or user home directories).
  4. Review job build logs for archive extraction activity
    Examine recent build logs for any steps that unpack .tar or .tar.gz files. Look for patterns such as 'Extracting', 'tar', 'untar', 'unarchive', or similar operations in console output.
    Affected if Build logs show extraction of .tar or .tar.gz archives from untrusted sources.
  5. Audit Configure Permission settings for users
    Navigate to Manage Jenkins > Manage Users and check which authenticated users have Configure permissions (Manage Jenkins > Configure Global Security). Verify which users can create or modify jobs that could trigger archive extraction.
    Affected if Multiple authenticated users or groups have Configure or Job/Configure permissions, allowing them to supply malicious archives.

You are affected if your Jenkins version is below 2.555 (weekly) or 2.541.3 (LTS) AND you use features that extract .tar or .tar.gz archives from sources controlled by users with job configuration permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.541.3 / 2.555 or later
Fixed in 2.541.32.555
Interim mitigation

Upgrade Jenkins to a patched version beyond 2.554 (or LTS beyond 2.541.2) that implements safe symlink handling during archive extraction, and ensure the Jenkins process runs with minimal filesystem privileges.

Recommended fix High confidence

Jenkins 2.555 or later, or Jenkins LTS 2.541.3 or later

  1. 1. Back up the Jenkins home directory and any custom configurations
  2. 2. Review the Jenkins LTS upgrade guide for any breaking changes between current version and 2.541.3
  3. 3. Upgrade Jenkins to version 2.555 or later (or LTS 2.541.3 or later)
  4. 4. After upgrade, verify the Jenkins controller starts successfully
  5. 5. Confirm plugins and jobs function correctly post-upgrade
  6. 6. Restrict Item/Configure permissions to trusted users only to prevent exploitation
Caveat Review LTS upgrade guide for breaking changes; some plugins may require updates compatible with the new Jenkins version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data