Mcp ServerApplication · Jenkins

CVE-2025-64132

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-29

Fix available

A fix is available. Upgrade to 0.86.v7d3355e6a_a_18 or later.

See remediation →

60/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

Jenkins MCP Server Plugin 0.84.v50ca_24ef83f2 and earlier does not perform permission checks in multiple MCP tools, allowing attackers to trigger builds and obtain information about job and cloud configuration they should not be able to access.

Technical summary

dbcve analysis · moderate confidence

The Jenkins MCP Server Plugin versions 0.84 and earlier lacks authorization checks on multiple MCP tool endpoints, allowing authenticated users with limited or no permissions to trigger builds and access sensitive job and cloud configuration details they should not be able to view or modify.

MitigationUpgrade to Jenkins MCP Server Plugin version 0.85 or later which implements proper permission checks on all MCP tool endpoints.

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

Affected products & versions

NVD · CPE data

Mcp ServerApplication

Affected:< 0.86.v7d3355e6a_a_18

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

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

Verify Jenkins MCP Server Plugin is installed

Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Jenkins MCP Server' or 'MCP Server' in the list of installed plugins

Affected if The plugin appears in the installed plugins list
Check the installed version of Jenkins MCP Server Plugin

In the same Installed Plugins list, locate the Jenkins MCP Server entry and note the Version column value

Affected if Version is 0.84 or earlier, or matches the pattern 0.86.v7d3355e6a_a_18 or lower
Identify users with limited permissions who have MCP access

Review user permissions in Manage Jenkins > Manage Users, and check if any users with Overall/Read restrictions or limited Job permissions have API access or session tokens

Affected if Users with restricted permissions (such as Overall/Read set to Deny or limited Job/Read permissions) exist and have access to MCP Server endpoints
Inspect MCP tool endpoint configuration

Review Jenkins configuration files (config.xml) or MCP Server configuration for exposed endpoints, looking for tool definitions related to builds, jobs, or cloud configuration

Affected if MCP tool endpoints are exposed and accessible without proper permission validation in the plugin configuration

Your environment is affected if the Jenkins MCP Server Plugin is installed at version 0.84 or earlier, particularly when users with limited permissions have access to MCP functionality.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 0.86.v7d3355e6a_a_18 or later

Fixed in 0.86.v7d3355e6a_a_18

Interim mitigation

Upgrade to Jenkins MCP Server Plugin version 0.85 or later which implements proper permission checks on all MCP tool endpoints.

Recommended fix High confidence

0.86.v7d3355e6a_a_18 or later

Log in to Jenkins as an administrator
Navigate to 'Manage Jenkins'
Go to 'Manage Plugins'
Select the 'Installed' tab
Locate the 'MCP Server' plugin in the list
If an update is available, click 'Update' to install version 0.86.v7d3355e6a_a_18 or later
Alternatively, navigate to 'Available' tab, search for 'MCP Server', and install the latest version which contains the fix
After installation, restart Jenkins or wait for the plugin to load

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

Fix this in Mcp Server Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-64132 — 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

Primary sources

www.jenkins.ioVendor Advisory
www.openwall.comMailing ListThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-64132?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 0.86.v7d3355e6a_a_18 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Mcp Server

Remediation

Need this fixed?

Fix this in Mcp Server 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-64132 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References