CVE-2025-67637

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.

Published: 2025-12-10 Last update: 2025-12-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-67637 is rated Low Risk (22.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-67637

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-28 0.03% 0.05% +0.02%
2 2025-12-27 0.05% 0.03% -0.02%
3 2025-12-19 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-67637

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-67637

GitHub Security Advisory for CVE-2025-67637

GHSA-fxj7-6v9w-xc76 · Severity: medium · Ecosystem: maven — Jenkins's build authorization token is stored and displayed in plain text

OS Trackers for CVE-2025-67637

vendor priority summary link
alpine — CVE-2025-67637: 1 source package rows (jenkins); 33 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 33. https://security.alpinelinux.org/vuln/CVE-2025-67637
redhat medium — https://access.redhat.com/security/cve/CVE-2025-67637

Affected software / configurations for CVE-2025-67637

Vendor Product Version Raw CPE
jenkins jenkins < 2.528.3 cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*
jenkins jenkins < 2.541 cpe:2.3:a:jenkins:jenkins:*:*:*:*:-:*:*:*

References for CVE-2025-67637

cvelogic Threat Intelligence