Compliance Impact

The vulnerability allows server-side request forgery (SSRF) that can be exploited to probe internal Jenkins-adjacent or private network services, posing significant confidentiality risks.

Such confidentiality risks could potentially lead to unauthorized access or exposure of sensitive data, which may impact compliance with data protection regulations like GDPR or HIPAA that require safeguarding personal and sensitive information.

However, the provided information does not explicitly detail the direct effects on compliance with these standards or any specific regulatory implications.

Useful 0 Not Useful 0

Executive Summary

CVE-2026-10276 is a Server-Side Request Forgery (SSRF) vulnerability found in the Jenkins-server-mcp tool, specifically affecting the jobPath parameter used in functions like get_build_status, get_build_log, and trigger_build.

The vulnerability occurs because the jobPath parameter, which is user-controlled, is directly concatenated into Axios request URLs without proper validation. If jobPath starts with a forward slash (/), it can create a protocol-relative URL that bypasses the intended Jenkins server URL and allows requests to arbitrary internal or attacker-controlled hosts.

An attacker can exploit this remotely by providing a malicious jobPath value, causing the server to send requests to unintended targets within the internal network or external hosts accessible to the server.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to significant confidentiality risks by allowing attackers to probe internal Jenkins-adjacent or private network services that are normally inaccessible.

The integrity and availability impacts are considered low to moderate, depending on the endpoints exposed by the SSRF attack.

Overall, an attacker with network access to the server can use this flaw to make unauthorized requests to internal systems, potentially exposing sensitive information or causing unintended interactions with internal services.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by monitoring for unusual or unauthorized outbound requests originating from the Jenkins-server-mcp tool, especially those involving the jobPath parameter with leading slashes or protocol-relative URLs.

A proof of concept involves sending requests with jobPath values starting with a forward slash (e.g., "/127.0.0.1:7777/jenkins-ssrf") which triggers outbound requests to internal or attacker-controlled hosts.

To detect exploitation attempts, you can monitor network traffic for unexpected requests to internal IPs or unusual ports from the Jenkins-server-mcp server.

• Use network monitoring tools (e.g., tcpdump, Wireshark) to capture outbound HTTP requests from the Jenkins-server-mcp host.
• Check application logs for requests to MCP tools (get_build_status, get_build_log, trigger_build) with jobPath parameters starting with slashes or unusual URL patterns.
• Example command to monitor outbound HTTP requests on port 80 or 443: sudo tcpdump -i any tcp port 80 or tcp port 443 -nn
• Example command to search logs for suspicious jobPath usage: grep -E 'jobPath=.*(/|\\|http|https|//)' /path/to/jenkins-server-mcp/logs/*

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include validating and sanitizing the jobPath parameter to reject values that start with slashes, backslashes, schemes (http, https), or protocol-relative paths.

Blocking requests that target loopback or internal network destinations can reduce the risk of SSRF exploitation.

Use safe path-join routines to normalize jobPath inputs as Jenkins components rather than allowing direct URL concatenation.

Until an official patch is released, restrict network access from the Jenkins-server-mcp server to only trusted endpoints to limit potential SSRF impact.

Monitor for suspicious activity and consider disabling or limiting the use of MCP tools that accept user-controlled jobPath parameters.

Useful 0 Not Useful 0