CVE-2025-64132 is a medium-severity (CVSS 5.4) CWE-862 vulnerability in io.jenkins.plugins:mcp-server. A fix is available for io.jenkins.plugins:mcp-server — see the affected versions and patch details below.
Jenkins MCP Server Plugin does not perform permission checks in multiple MCP tools
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-64132.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.jenkins.plugins:mcp-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins MCP Server Plugin 0.84.v50ca_24ef83f2 and earlier does not perform permission checks in several MCP tools.
This allows to do the following:
-
Attackers with Item/Read permission can obtain information about the configured SCM in a job despite lacking Item/Extended Read permission (
getJobScm). -
Attackers with Item/Read permission can trigger new builds of a job despite lacking Item/Build permission (
triggerBuild). -
Attackers without Overall/Read permission can retrieve the names of configured clouds (
getStatus).
MCP Server Plugin 0.86.v7d3355e6a_a_18 performs permission checks for the affected MCP tools.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:mcp-server | all versions | 0.86.v7d3355e6aio.jenkins.plugins:mcp-server:0.86.v7d3355e6a |
Affected Products
mcp serverjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:mcp-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:mcp-server to 0.86.v7d3355e6a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-64132 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-64132 in your dependencies?
Find it across Maven, including transitive dependencies.