Jenkins MCP Server Plugin does not perform permission checks in multiple MCP tools

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-64132: 0.26% estimated exploitation activity in the next 30 days; percentile 18.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins MCP Server Plugin 0.84.v50ca24ef83f2 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.v7d3355e6aa18 performs permission checks for the affected MCP tools.

Published by the source

29 Oct 2025, 15:31 UTC

Last modified by the source

5 Nov 2025, 20:52 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mrpq-9jr3-rqq9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64132

Advisory: Jenkins MCP Server Plugin does not perform permission checks in multiple MCP tools
IDs: CVE-2025-64132, GHSA-mrpq-9jr3-rqq9
Record: https://patchnext.com/advisories/cve-2025-64132 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.jenkins.plugins:mcp-server 0.86.v7d3355e6a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.plugins:mcp-server: affected < 0.86.v7d3355e6a; fixed in 0.86.v7d3355e6a

## Suggested inspection (read-only)
- Maven io.jenkins.plugins:mcp-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.jenkins.plugins:mcp-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mrpq-9jr3-rqq9 (GitHub-reviewed advisory GHSA-mrpq-9jr3-rqq9 lists affected ranges: Maven io.jenkins.plugins:mcp-server >=0 <0.86.v7d3355e6a)

Commands are suggestions: review each one before running it.