CVE-2025-67642VulnerabilityPublished 10 Dec 2025

CVE-2025-67642: Jenkins HashiCorp Vault Plugin · Vulnerability

Affects Jenkins HashiCorp Vault PluginSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jenkins Project Jenkins HashiCorp Vault Plugin	Affected =0	Fixed in–

AI-suggested

1. Immediately audit and restrict Item/Configure permissions in Jenkins to only trusted and necessary users to minimize the attack surface. 2. Monitor Jenkins logs and Vault access logs for unusual or unauthorized access patterns to detect potential exploitation attempts early. 3. Apply the vendor patch or update the Jenkins HashiCorp Vault Plugin to a fixed version as soon as it becomes available. 4. Implement network segmentation and least privilege principles around Jenkins and Vault infrastructure to limit the impact of credential compromise. 5. Use Vault's built-in audit logging and rotation policies to detect and mitigate credential misuse. 6. Consider temporary disabling the Vault plugin or limiting its use in critical pipelines until a patch is applied. 7. Educate Jenkins administrators and developers about the risks of excessive permissions and the importance of secure plugin management. 8. Employ multi-factor authentication (MFA) for Jenkins access to reduce the risk of compromised user accounts being leveraged to exploit this vulnerability.

Description

Jenkins HashiCorp Vault Plugin 371.v884a_4dd60fb_6 and earlier does not set the appropriate context for Vault credentials lookup, allowing attackers with Item/Configure permission to access and potentially capture Vault credentials they are not entitled to.

Impact

For European organizations, the impact of CVE-2025-67642 can be severe. Jenkins is widely used across Europe for continuous integration and continuous deployment (CI/CD) pipelines, and HashiCorp Vault is a popular secrets management solution. Unauthorized access to Vault credentials can lead to exposure of sensitive infrastructure secrets, enabling attackers to compromise cloud environments, databases, or other critical systems. This can result in data breaches, service disruptions, and loss of intellectual property. The vulnerability undermines the confidentiality of secrets, potentially leading to integrity and availability issues if attackers use stolen credentials to manipulate or disrupt systems. Since exploitation requires Item/Configure permissions, the threat is particularly relevant in organizations with broad or poorly controlled Jenkins permissions. The risk is amplified in sectors with stringent compliance requirements such as finance, healthcare, and critical infrastructure, common in countries like Germany, France, and the UK. Additionally, the exposure of Vault credentials could facilitate further attacks against European cloud providers or internal services, increasing the overall threat landscape.

CWE-282Improper Ownership Management (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Using Malicious Files (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jenkins.io/security/advisory/2025-12-10/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Dec 2025, 17:12 UTC

WeaknessesCWE-282

Technical details

References

Community reviews

Related threats