Jenkins Stack Hammer Plugin Stores API Keys Unencrypted in Job `config.xml` Files

published 2025-04-02 19 mo ago modified 2026-06-17 4 mo ago also GHSA-2wxq-944j-5g2v , EUVD-2025-9534

cvss: 5.5; 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 21%
public exploits: 0; none known

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.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 19 mo ago (2025-04-02)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	5.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
CNA	3.1	5.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
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:stackhammer	<=1.0.6	no fix listed

Affected products

Jenkins Project Jenkins Stack Hammer Plugin

Classification

Weakness

CWE-284 Improper Access Control
CWE-312 Cleartext Storage of Sensitive Information

References

jenkins.io /security/advisory/2025-04-02/#SECURITY-3520
vendor-advisory, web
nvd.nist.gov /vuln/detail/CVE-2025-31726
advisory
github.com /jenkinsci/stackhammer-plugin
package

Sources

Fencer Vulns 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.

Summary