CVE-2025-53661 json
Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form
published last yr. modified 4mo ago also GHSA-8wp4-r84g-gcmw , EUVD-2025-20853
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
Jenkins Testsigma Test Plan run Plugin 1.6 and earlier does not mask Testsigma API keys displayed on the job configuration form, increasing the potential for attackers to observe and capture them.
Is CVE-2025-53661 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.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins.plugins:testsigma | <=1.6 |
no fix listed |
Affected products
- Jenkins Project Jenkins Testsigma Test Plan run Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
jenkins.io
/security/advisory/2025-07-09/#SECURITY-3515
vendor-advisory, web
-
openwall.com
/lists/oss-security/2025/07/09/4
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-53661
advisory
-
github.com
/jenkinsci/testsigma-plugin
package
Sources
- CVE List CVE-2025-53661
- GitHub Advisory GHSA-8wp4-r84g-gcmw
- NVD CVE-2025-53661
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.