Jenkins's build authorization token is stored and displayed in plain text
Published Dec 10, 2025 · Updated Oct 22, 2026 · Also known as BIT-jenkins-2025-67637, GHSA-fxj7-6v9w-xc76
Original summary
Normalized public record · Updated Oct 22, 2026
Jenkins's build authorization token is stored and displayed in plain text
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
Jenkins 2.540 and earlier, LTS 2.528.2 and earlier stores build authorization tokens unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- BIT-jenkins-2025-67637, GHSA-fxj7-6v9w-xc76
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Dec 10, 2025 · Last refreshed Oct 22, 2026