CVE-2025-67637 Jenkins's build authorization token is stored and displayed in plain text

Medium 4.3 Published Updated

Attackers with extended read permissions or file system access can view unencrypted build authorization tokens in Jenkins configuration files.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-67637?

CVE-2025-67637 is a medium-severity vulnerability in Jenkins Jenkins, published on 10 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-312

Which versions are affected by CVE-2025-67637?

5 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core and jenkins. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.main:jenkins-core MavenAll versions2.528.3
org.jenkins-ci.main:jenkins-core MavenAll versions2.528.3
org.jenkins-ci.main:jenkins-core MavenFrom 2.5292.541
org.jenkins-ci.main:jenkins-core MavenFrom 2.5292.541
jenkins BitnamiAll versions2.528.3, 2.541.0

Products include Jenkins Jenkins.

How do I fix CVE-2025-67637?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.528.3 or 2.541.

Is CVE-2025-67637 being exploited?

There is no known exploitation of CVE-2025-67637 in the wild and no public exploit code.

All Jenkins Jenkins vulnerabilities

Sources

Also known as BIT-jenkins-2025-67637, GHSA-fxj7-6v9w-xc76, MINI-52hh-jpxv-w35c, MINI-gp9q-cwqf-p47j, MINI-h858-qhxf-8c3f, MINI-pm54-9gxr-8vmw and 1 more.

Is CVE-2025-67637 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free