CVE-2026-10276
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 · uneditedA vulnerability has been found in hekmon8 Jenkins-server-mcp 0.1.0. This vulnerability affects the function jobPath of the file src/index.ts of the component get_build_status/get_build_log/trigger_build. Such manipulation leads to server-side request forgery. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceServer-side request forgery (SSRF) in hekmon8 Jenkins-server-mcp v0.1.0. The jobPath function in src/index.ts (used by get_build_status, get_build_log, and trigger_build components) allows remote attackers to manipulate the function to make the server fetch unintended URLs, potentially accessing internal services, cloud metadata endpoints, or internal network resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Jenkins-server-mcp plugin is installedCheck the Jenkins plugin directory or plugin manager for 'jenkins-server-mcp' or list installed plugins via Jenkins CLI/APIAffected if The plugin appears in the list of installed plugins
-
Verify the plugin versionLocate the plugin's manifest or version file, typically found in $JENKINS_HOME/plugins/jenkins-server-mcp/ or via Jenkins plugin manager detailsAffected if The installed version is 0.1.0 exactly
-
Confirm vulnerable functions are accessibleCheck if the MCP server exposes get_build_status, get_build_log, or trigger_build operations by examining the plugin configuration or API endpointsAffected if Any of these three operations are exposed and accessible to users
-
Inspect jobPath parameter handlingReview the plugin configuration or logs for how jobPath parameters are processed; check if any validation exists for the input before making HTTP requestsAffected if No input validation is configured for the jobPath parameter
-
Check network configuration for outbound requestsExamine Jenkins system configuration or plugin settings to determine if there are restrictions on outbound HTTP requests from the Jenkins serverAffected if The Jenkins server can make arbitrary HTTP requests to external or internal URLs without restrictions
The environment is affected if the Jenkins-server-mcp plugin version 0.1.0 is installed and the vulnerable operations (get_build_status, get_build_log, trigger_build) are accessible without input validation on the jobPath parameter.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict input validation and allowlist enforcement on the jobPath parameter to restrict URLs to expected Jenkins endpoints only. Consider network segmentation to limit outbound connections from the server.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10276 in production — separate from our analysis above.
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.
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.
- 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