# CVE-2025-64135: Jenkins Eggplant Runner Plugin protection mechanism disabled

> The plugin disables Java's tunneling authentication protection, allowing attackers to bypass security controls intended to prevent credential leakage during proxy connections.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-w5r3-gr8w-7fj5

## What is CVE-2025-64135?

CVE-2025-64135 is a medium-severity vulnerability in Jenkins Eggplant Runner Plugin, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2025-64135?

2 open source packages ship an affected version, including io.jenkins.plugins:eggplant-runner. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:eggplant-runner` | Maven | All versions to 0.0.1.301.v963cffe8ddb | None |
| `io.jenkins.plugins:eggplant-runner` | Maven | All versions to 0.0.1.301.v963cffe8ddb | None |

Products: Jenkins Eggplant Runner.

## How do I fix CVE-2025-64135?

No fix has been published for CVE-2025-64135 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64135 being exploited?

There is no known exploitation of CVE-2025-64135 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64135 and fix it if it is affected.

What it is: CVE-2025-64135 is a medium-severity vulnerability in Jenkins Eggplant Runner Plugin, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64135 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:eggplant-runner (Maven): affected all versions up to 0.0.1.301.v963cffe8ddb; no fix listed
- io.jenkins.plugins:eggplant-runner (Maven): affected all versions up to 0.0.1.301.v963cffe8ddb; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64135/ (Markdown: https://insights.sbomify.com/CVE-2025-64135/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64135
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64135
- OSV: https://osv.dev/vulnerability/CVE-2025-64135

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64135/
Summaries are generated and may contain mistakes; the official description above is the record.