Jenkins Project · Jenkins · published 2026-05-27
CVE-2026-48922
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-48922 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This Jenkins vulnerability: CVSS 7.5 (v3.1), a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
CI/CDJenkins
Jenkins: Jenkins Security Advisory 2026-05-27
Why: Vendor security release for server software (most severe: CVE-2026-48920).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (29th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.5 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Jenkins Project Jenkins Credentials Binding Plugin
0through720.v3f6decef43ea_(affected)
Description (from the CVE record)#
Jenkins Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, allowing attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem, which can lead to remote code execution if Jenkins is configured to allow a low-privileged user to configure file or zip file credentials used for a job running on the built-in node.
Quoted from the CVE Program record.