CVE-2025-53668 json
Jenkins VAddy Plugin vulnerability exposes unencrypted keys to certain authenticated users
published last yr. modified 4mo ago also GHSA-mr49-vmp6-2pwq , EUVD-2025-20846
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Jenkins VAddy Plugin 1.2.8 and earlier stores Vaddy API Auth Keys unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Is CVE-2025-53668 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:vaddy-plugin | <=1.2.8 |
no fix listed |
Affected products
- Jenkins Project Jenkins VAddy Plugin
Classification
- Weakness
-
- CWE-311 Missing Encryption of Sensitive Data
References
-
jenkins.io
/security/advisory/2025-07-09/#SECURITY-3527
vendor-advisory, web
-
openwall.com
/lists/oss-security/2025/07/09/4
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-53668
advisory
-
github.com
/jenkinsci/vaddy-plugin
package
Sources
- CVE List CVE-2025-53668
- GitHub Advisory GHSA-mr49-vmp6-2pwq
- NVD CVE-2025-53668
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.