CVE-2025-31726: Jenkins Stack Hammer Plugin 1.0.6 and earlier stores Stack Hammer API keys unencrypted in job config.xml files
CVE-2025-31726 is a medium-severity flaw (CVSS 5.5) affecting stack hammer. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Jenkins Stack Hammer Plugin 1.0.6 and earlier stores Stack Hammer API keys unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 79%) |
| CISA exploited list | No |
| Weakness | CWE-284 |
| Published | 2025-04-02 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-31726?
stack hammer: upgrade to newer than 1.0.6. Exact commands for each OS are on this page.
Is CVE-2025-31726 being exploited?
CVE-2025-31726 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-31726 affect?
CVE-2025-31726 affects stack hammer. Severity is medium (CVSS 5.5). Jenkins Stack Hammer Plugin 1.0.6 and earlier stores Stack Hammer API keys unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller fi
How urgent is CVE-2025-31726?
Priority 25/100. No elevated risk signals yet.