API token disclosure via plaintext job configuration
Published Oct 29, 2025 · Updated Oct 29, 2025
Cleartext storage in Jenkins' ByteGuard Build Actions Plugin 1.0 and earlier allows remote authenticated users to read API tokens via job access. The plugin writes configured API tokens without encryption into job config.xml files on the Jenkins controller. Item/Extended Read permission or controller-filesystem access is required, and the reported impact is limited to token disclosure.
Summary
What happened
Cleartext storage in Jenkins' ByteGuard Build Actions Plugin 1.0 and earlier allows remote authenticated users to read API tokens via job access. The plugin writes configured API tokens without encryption into job config.xml files on the Jenkins controller. Item/Extended Read permission or controller-filesystem access is required, and the reported impact is limited to token disclosure.
The record
- CVE
- CVE-2025-64144
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Jenkins Project
- Product
- ByteGuard Build Actions Plugin
- Classifications
- CWE-311, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo