Jenkins
CVE-2025-67636
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Jenkins with View/Read permission
-
ExploitOpen affected view containing secrets
-
ImpactRead exposed encrypted password values
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated Jenkins user who already holds the View/Read permission on an affected instance (Jenkins 2.540 or earlier, or LTS 2.528.2 or earlier) and requires that a view containing password values exists to be displayed. Key limiting factors: the attacker must be a provisioned, authenticated account (PR:L), no privilege escalation beyond that is possible, and the values returned are encrypted rather than plaintext - so direct secret recovery depends on separately defeating Jenkins' encryption or reusing the encrypted form. No user interaction by a victim is needed. |
| Impact | This is a low-to-moderate priority information-disclosure issue, not a high-urgency flaw. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) signals network reach and low complexity, but PR:L means the attacker must already be an authenticated Jenkins user holding View/Read permission, and impact is confined to confidentiality only (C:L, no integrity/availability). The description further notes that only the ENCRYPTED password values are exposed, not decrypted plaintext, which caps the practical damage unless an attacker can separately break or reuse those encrypted blobs. All exploitation signals point the same direction and are consistent: EPSS is 0.25% (15th percentile), there is no CISA KEV listing, and no public exploit is identified - a low-likelihood, low-impact profile with no conflicting indicators. One data caveat: the input Tags label this 'Authentication Bypass,' which conflicts with CWE-862 (Missing Authorization) and the description's own framing of a missing PERMISSION check against an already-authenticated user - this is an authorization/permission-check defect, not an authentication bypass. |
| Exploit ScenarioDerived | A low-privileged Jenkins user who only holds View/Read permission opens a configured view and reads encrypted password values that should have been hidden from them due to insufficient permissions. No public exploit code is required or known; the data is exposed through normal UI access once the user is authenticated to the affected instance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Jenkins 2.540 and earlier, along with Jenkins LTS 2.528.2 and earlier, allow an authenticated user who already holds View/Read permission to view encrypted password values exposed in views because of a missing permission check. The disclosure is limited to encrypted rather than plaintext secrets, so turning the exposure into usable credentials requires separately defeating Jenkins' encryption or reusing the encrypted form; no public exploit code has been identified at time of analysis and EPSS is low (0.25%, 15th percentile). This is a low-to-moderate priority information-disclosure issue rather than a high-urgency flaw.
RemediationAI
Apply the fix described in the vendor advisory at https://www.jenkins.io/security/advisory/2025-12-10/#SECURITY-1809; the advisory is the authoritative source for the exact patched weekly or LTS release numbers, which are not specified in the provided data. Until upgrading, the most direct compensating control is to restrict the View/Read permission to trusted, provisioned accounts only, because the issue requires an authenticated user who already holds that permission; the trade-off is that legitimate users may lose read access to views. Additionally, audit views for embedded encrypted password values and remove or relocate credential material out of view definitions where feasible, and if you cannot rule out that the encryption layer was separately broken, rotate any credentials whose encrypted values may have been exposed; because the exposed values are encrypted, emergency rotation is lower priority than it would be for plaintext secret disclosure, but rotation still causes service interruptions. Monitor Jenkins access and audit logs for unusual view rendering by low-privilege users as a detection measure.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in maven
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-862, Missing Authorization: Jenkins failed to enforce the permission boundary that should prevent users with only View/Read permission from seeing encrypted password values rendered as part of view definitions. Jenkins organizes jobs into views, and View/Read is a granular permission intended to allow browsing but not necessarily to expose configuration details. Under the hood, Jenkins stores credentials and secret material encrypted using a master key (through hudson.util.Secret), so what is exposed is the ciphertext form, not the recoverable cleartext. The provided CPE entries identify the affected core distributions precisely: cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:* for the LTS line (2.528.2 and earlier) and cpe:2.3:a:jenkins:jenkins:*:*:*:*:-:*:*:* for the weekly line (2.540 and earlier). The CVSS vector (AV:N/AC:L/PR:L/UI:N) confirms the attack is network-reachable, requires a low-privileged authenticated account, and needs no victim interaction; the assessed limiting factors are that the attacker must already be a provisioned user with View/Read, no privilege escalation beyond that is possible, and the values returned are encrypted rather than decrypted secrets.
Know when Jenkins gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Authenticated View/Read user over the network (PR:L, AV:N, AC:L); only encrypted secrets leak, so confidentiality is Low and there is no integrity or availability impact.
Primary rating from Vendor (googlegroups).
CVSS VectorVendor: googlegroups
DescriptionCVE.org
A missing permission check in Jenkins 2.540 and earlier, LTS 2.528.2 and earlier allows attackers with View/Read permission to view encrypted password values in views.
Blast Radius
ecosystem impact- 1 maven packages depend on org.jenkins-ci.main:jenkins-core (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 2.529.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Affected Products (CPE)CVE.org
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/
The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary co
The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a
Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to ex
The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive j
The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and ea
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.50 and earlier in src/main/java/org/jenkinsci/
A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in. Rated high severity (CVSS 8.
A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB