VulnerabilityPublished 29 Oct 2025Updated 4 Nov 2025

CVE-2025-64135: Jenkins Eggplant Runner Plugin · Insecure Default

Affects Jenkins Eggplant Runner PluginSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 29 Oct 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 26 Oct 2026.

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 Eggplant Runner Plugin	Affected =0	Fixed in–

AI-suggested

1. Monitor Jenkins plugin updates closely and apply patches for the Eggplant Runner Plugin as soon as they become available to restore the default security settings for `jdk.http.auth.tunneling.disabledSchemes`. 2. Until a patch is released, manually override the Java system property by setting `jdk.http.auth.tunneling.disabledSchemes` to its default secure value (e.g., `Basic, Digest, NTLM, Negotiate`) in the Jenkins runtime environment or plugin configuration to re-enable protection. 3. Restrict the use of the Eggplant Runner Plugin to trusted environments and limit network access to Jenkins servers to reduce exposure. 4. Implement network monitoring and anomaly detection focused on HTTP proxy tunneling traffic to identify unusual authentication attempts or credential leakage. 5. Enforce strict access controls and credential management policies for Jenkins and related systems to minimize the impact of any leaked credentials. 6. Educate DevOps and security teams about this vulnerability to ensure rapid response and awareness of proxy tunneling risks. 7. Consider isolating Jenkins build environments and using encrypted communication channels to reduce the risk of interception.

Description

Jenkins Eggplant Runner Plugin 0.0.1.301.v963cffe8ddb_8 and earlier sets the Java system property `jdk.http.auth.tunneling.disabledSchemes` to an empty value, disabling a protection mechanism of the Java runtime.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the confidentiality of sensitive information, such as authentication credentials used in HTTP proxy tunneling scenarios. Organizations heavily reliant on Jenkins for software development and deployment, especially those integrating Eggplant Runner Plugin in their CI/CD pipelines, could see increased risk of credential leakage. This could lead to unauthorized access to internal systems or further lateral movement within networks if attackers intercept these credentials. The impact is heightened in environments with complex proxy configurations or where sensitive data is transmitted over HTTP tunnels. While the vulnerability does not affect integrity or availability directly, the potential for credential compromise can indirectly lead to broader security incidents. Given the widespread use of Jenkins in European tech sectors, including finance, manufacturing, and government, the vulnerability could affect critical infrastructure and sensitive projects. The absence of known exploits reduces immediate risk, but the medium CVSS score and ease of remote exploitation without authentication warrant proactive mitigation.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2025, 15:52 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats