Jenkins ByteGuard Build Actions Plugin does not mask API tokens displayed on the job configuration form

published 2025-10-29 12 mo ago modified 2026-10-08 32 d ago also GHSA-vmm2-53rc-43v3 , EUVD-2025-36653

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

Jenkins ByteGuard Build Actions Plugin 1.0 does not mask API tokens displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 12 mo ago (2025-10-29)

Exploit prediction

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

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	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	io.jenkins.plugins:byteguard-build-actions	<=1.0	no fix listed

Affected products

Jenkins Project Jenkins ByteGuard Build Actions Plugin

Classification

Weakness

CWE-311 Missing Encryption of Sensitive Data

References

jenkins.io /security/advisory/2025-10-29/#SECURITY-3560
vendor-advisory, web
openwall.com /lists/oss-security/2025/10/29/2
web
nvd.nist.gov /vuln/detail/CVE-2025-64145
advisory
github.com /jenkinsci/byteguard-build-actions-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