Jenkins's build authorization token is stored and displayed in plain text
Date: 2025-12
Affected: maven/org.jenkins-ci.main:jenkins-core, maven/org.jenkins-ci.main:jenkins-core
Attack vector: command-injection
Category: vulnerability-disclosure
Severity: Medium
CVE: CVE-2025-67637
CVE-2025-67640
CWE: CWE-312
CWE-78
CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)

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.


Mitigations:

Architectural layers (MAESTRO):