SSRF Vulnerability in Sentry MCP Server Exposes Security Risks

SSRF Vulnerability in Sentry MCP Server Exposes Security Risks

First seen 28 Aug 2026, 14:23 UTC Forkast.NewsCryptorankwww.tenable.comwww.ox.security 64.5

Article Content

Browse articles
ThreatCluster

On July 12, 2026, researcher cccccccti disclosed a Server-Side Request Forgery (SSRF) vulnerability in the raw_sentry_api component of ddfourtwo/sentry-selfhosted-mcp, tracked as CVE-2026-81421. This vulnerability allows attackers to force Axios to call arbitrary endpoints, with a public exploit already available. As of August 27, 2026, the maintainer has not responded to the disclosure, leaving many systems exposed. Industry data indicates that 36.7% of 7,000 scanned MCP servers are vulnerable, and 41% lack authentication. Trend Micro identified 492 MCP servers exposed to the internet without authentication. This incident is linked to broader security issues in the Model Context Protocol (MCP) ecosystem, which has seen a shift in security responsibilities. The situation is exacerbated by a recent update that removed session-level security measures, creating new attack surfaces. The vulnerability poses significant risks for crypto infrastructure and related integrations.

Key Points: • CVE-2026-81421 allows SSRF attacks via unvalidated Axios requests. • 36.7% of scanned MCP servers are vulnerable, with 41% lacking authentication. • Public exploit available, and maintainer has not responded for 46 days.

Timeline

2026-05-08
CVE-2026-42271 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-07-12
SSRF vulnerability disclosed
Researcher cccccccti reported CVE-2026-81421 in the raw_sentry_api component.
Forkast.News
2026-07-28
CVE-2026-16498 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-08-26
CVE-2026-81421 published
The SSRF vulnerability was officially published with a CVSS score of 7.3 by Tenable.
Cryptorank
2026-08-27
Maintainer silence noted
46 days passed without a response from the maintainer since the vulnerability disclosure.
Forkast.News