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

CVE-2025-67638 · Severity: medium · CVSS 4.3 · Published 2025-12-10

Jenkins 2.540 and earlier, LTS 2.528.2 and earlier does not mask build authorization tokens displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

Technologies: Jenkins, org.jenkins-ci.main:jenkins-core (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2025-67638 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-67638 being exploited in the wild.
How severe is CVE-2025-67638?
Medium severity, with a CVSS score of 4.3, published 10 December 2025.
Which products and versions are affected?
org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=2.529,fixed=2.541.
Is there a fix for CVE-2025-67638?
Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.541 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-67638?
Check whether you run Jenkins or org.jenkins-ci.main:jenkins-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.541 or later
    # set org.jenkins-ci.main:jenkins-core to 2.541 in your pom.xml or build.gradle

Affected products

  • Jenkins
  • org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=2.529,fixed=2.541

Identifiers

  • CVE-2025-67638
  • GHSA-hxjg-2jvf-h3rx

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.