Jenkins has a link following vulnerability allows arbitrary file creationGHSA-r6qv-frpc-q66c
HIGHFix: jenkinsci/jenkins@6dc9993GHSA-r6qv-frpc-q66c 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.
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 GHSA-r6qv-frpc-q66c.
EPSS Exploitation Probability
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
org.jenkins-ci.main:jenkins-coreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.555org.jenkins-ci.main:jenkins-core:2.555 |
Affected Products
jenkinsjenkinsDetection & mitigation playbook
Open-source dependencyDetect
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 GHSA-r6qv-frpc-q66c 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.
| 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
Is GHSA-r6qv-frpc-q66c in your dependencies?
Find it across Maven, including transitive dependencies.