Skip to main content

sentry-selfhosted-mcp CVE-2026-81421

| EUVDEUVD-2026-66829 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-08-26 VulDB GHSA-77f3-qj56-x322
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify exposed MCP server endpoint
  2. Delivery
    Send unauthenticated raw_sentry_api invocation
  3. Exploit
    Supply crafted internal URL as endpoint argument
  4. Execution
    Server issues outbound HTTP request to internal target
  5. Persist
    Receive internal service response
  6. Impact
    Enumerate internal network or harvest credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The MCP server must be reachable over the network by the attacker - no authentication is required per PR:N in the CVSS 4.0 vector. The raw_sentry_api tool must be accessible to the calling client, which in MCP deployments is typically controlled by the MCP host configuration. No special server-side configuration is required beyond the default installation of version 0.4.0. Exploitation is limited by: the MCP server's network exposure (local-only deployments are not remotely exploitable), egress firewall rules that may block internal destination addresses, and the absence of a direct code execution primitive - impact is confined to SSRF-reachable services rather than arbitrary command execution.

Impact

The CVSS 4.0 vector scores 6.9 (Medium) with AV:N/AC:L/AT:N/PR:N/UI:N and impacts rated VC:L/VI:L/VA:L - indicating that unauthenticated remote exploitation is straightforward but individual impact per request is limited. The E:P modifier confirms publicly available exploit code exists, which elevates practical risk above the raw numeric score. No CISA KEV listing is present, so active exploitation at scale is not confirmed. SSRF vulnerabilities in API-proxy tools like this one carry disproportionate real-world risk relative to their CVSS score: successful exploitation can expose cloud metadata credentials, enumerate internal network topology, or pivot to services that trust the server's IP. The product's niche footprint (MCP server for self-hosted Sentry) limits mass exploitation, but any deployment with network-reachable MCP endpoints is concretely at risk. No EPSS data was provided in the source intelligence.

Exploit ScenarioDerived

An attacker with network access to an exposed sentry-selfhosted-mcp instance sends a crafted MCP tool invocation to raw_sentry_api with the endpoint parameter set to an internal address such as http://169.254.169.254/latest/meta-data/. The server fetches the resource and returns the response, leaking cloud instance metadata including IAM credentials. A public proof-of-concept demonstrating this technique exists in the project's GitHub issue tracker.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Server-side request forgery in ddfourtwo sentry-selfhosted-mcp 0.4.0 allows remote unauthenticated attackers to manipulate the endpoint argument in the raw_sentry_api component, causing the server to issue arbitrary HTTP requests to internal or external hosts. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required, and a public exploit exists via a GitHub issue report. No patch has been released - the project maintainer has not responded to the coordinated disclosure.

RemediationAI

No vendor-released patch has been identified at time of analysis - the maintainer had not responded to the issue report (https://github.com/ddfourtwo/sentry-selfhosted-mcp/issues/2) at time of disclosure. As a primary compensating control, restrict network access to the MCP server so that only trusted AI orchestration clients can invoke raw_sentry_api; deploying a firewall or VPC security group rule to block inbound connections from untrusted sources eliminates the remote unauthenticated attack vector at the cost of reduced accessibility. Additionally, configure egress filtering on the host running sentry-selfhosted-mcp to block outbound connections to RFC-1918 private ranges and cloud metadata addresses (169.254.169.254, fd00::/8), which prevents the most impactful SSRF pivots while permitting legitimate Sentry API calls. Monitor the GitHub repository for a patched release and prioritize upgrading once available.

Affected VersionsENISA

sentry-selfhosted-mcp 0.4.0

Affected Packages

euvd sentry_selfhosted_mcp no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

sentry-selfhosted-mcp is an MCP (Model Context Protocol) server designed to bridge AI tooling with self-hosted Sentry error-tracking instances. The vulnerable component, raw_sentry_api, exposes an endpoint parameter that is passed to outbound HTTP client calls without sufficient validation or allowlist enforcement - the textbook CWE-918 (Server-Side Request Forgery) pattern. An attacker who can invoke this MCP tool with a crafted endpoint value can redirect the server's HTTP client to arbitrary internal addresses, cloud metadata endpoints (e.g., 169.254.169.254), or other services reachable from the server's network. The CPE string cpe:2.3:a:ddfourtwo:sentry-selfhosted-mcp covers all versions, with version 0.4.0 explicitly confirmed as affected by VulDB.

Know when Sentry Selfhosted Mcp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.3 HIGH

Network-reachable, no auth or interaction required; limited CIA impact consistent with SSRF without code execution or scope change.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Aug 27, 2026 - 01:22 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
CVE Published
Aug 26, 2026 - 23:45 cve.org
MEDIUM 6.9

DescriptionCVE.org

A security flaw has been discovered in ddfourtwo sentry-selfhosted-mcp 0.4.0. The affected element is an unknown function of the component raw_sentry_api. The manipulation of the argument endpoint results in server-side request forgery. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Rare
niche MCP server for self-hosted Sentry, small user base
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy