First published: Wed Apr 02 2025(Updated: )
Jenkins Stack Hammer Plugin 1.0.6 and earlier stores Stack Hammer API keys unencrypted in job `config.xml` files on the Jenkins controller as part of its configuration. These API keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system. As of publication of this advisory, there is no fix.
Credit: jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Stack Hammer Plugin | <1.0.6 | |
maven/org.jenkins-ci.plugins:stackhammer | <=1.0.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-31726 is considered a medium severity vulnerability due to the potential exposure of sensitive API keys.
To fix CVE-2025-31726, upgrade the Jenkins Stack Hammer Plugin to version 1.0.7 or later.
CVE-2025-31726 introduces the risk of unauthorized users accessing unencrypted Stack Hammer API keys stored in job config.xml files.
Users of Jenkins Stack Hammer Plugin versions 1.0.6 and earlier are affected by CVE-2025-31726.
Potential impacts of CVE-2025-31726 include unauthorized access to API keys that could compromise application security.