Token disclosure via cleartext job configuration storage
Published Dec 10, 2025 · Updated Dec 10, 2025
Cleartext credential storage in Jenkins 2.540 and earlier and LTS 2.528.2 and earlier allows authenticated users to read build tokens. BuildAuthorizationToken stored the token as a String, and its XStream converter returned that raw value when serializing job configuration. Exposure requires Item/Extended Read permission or controller filesystem access and is limited to jobs that use build authorization tokens.
Summary
What happened
Cleartext credential storage in Jenkins 2.540 and earlier and LTS 2.528.2 and earlier allows authenticated users to read build tokens. BuildAuthorizationToken stored the token as a String, and its XStream converter returned that raw value when serializing job configuration. Exposure requires Item/Extended Read permission or controller filesystem access and is limited to jobs that use build authorization tokens.
The record
- CVE
- CVE-2025-67637
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-312, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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