dbcve.org
Eggplant RunnerApplication · Jenkins

CVE-2025-64135

MEDIUM · 5.9 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to after 0.0.1.301.v963cffe8ddb_8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Eggplant Runner Plugin sets the Java system property 'jdk.http.auth.tunneling.disabledSchemes' to an empty value, which removes a built-in Java security protection that restricts certain authentication schemes from being used in HTTP proxy tunneling. This allows potentially insecure authentication credentials to be transmitted through proxy tunnels, increasing the risk of credential theft or man-in-the-middle attacks.

MitigationUpgrade the Jenkins Eggplant Runner Plugin to a version newer than 0.0.1.301.v963cffe8ddb_8 that no longer disables this Java security mechanism, or remove the code that sets this property to an empty value if upgrading is not immediately possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Eggplant RunnerApplication
Affected:<= 0.0.1.301.v963cffe8ddb_8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Jenkins Eggplant Runner Plugin is installed
    List all installed Jenkins plugins via Jenkins UI (Manage Jenkins > Plugins > Installed) or by checking the $JENKINS_HOME/plugins directory for a folder named 'eggplant-runner' or 'eggplant-runner.jpi'
    Affected if The plugin folder or .jpi file exists in the Jenkins plugins directory
  2. Determine the installed version of Eggplant Runner Plugin
    Check the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin .jpi file, or view the version listed in the Jenkins UI plugin manager
    Affected if The version is 0.0.1.301.v963cffe8ddb_8 or earlier
  3. Verify the plugin is actively loaded and enabled
    Check Jenkins system information or the plugin status page to confirm the Eggplant Runner Plugin status shows as 'Active' or 'Enabled'
    Affected if The plugin status shows as active or enabled in Jenkins

A user is affected if the Jenkins Eggplant Runner Plugin version 0.0.1.301.v963cffe8ddb_8 or earlier is installed and enabled in their Jenkins instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.0.1.301.v963cffe8ddb_8
Interim mitigation

Upgrade the Jenkins Eggplant Runner Plugin to a version newer than 0.0.1.301.v963cffe8ddb_8 that no longer disables this Java security mechanism, or remove the code that sets this property to an empty value if upgrading is not immediately possible.

Recommended fix Moderate confidence

A fixed version newer than 0.0.1.301.v963cffe8ddb_8 (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to the Jenkins Manage Plugins page
  2. 2. Go to the 'Installed' tab and locate the Eggplant Runner plugin
  3. 3. Check for available updates for the Eggplant Runner plugin
  4. 4. If a newer version is available, select it and click 'Download now and install after restart' or 'Update'
  5. 5. Wait for the plugin to update and for Jenkins to restart
  6. 6. Verify the plugin has been updated to a version newer than 0.0.1.301.v963cffe8ddb_8
Caveat Review release notes for any breaking changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eggplant Runner Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data