Skip to main content
Mallory
CriticalVulnerability

CVE-2026-19516: Server-side request forgery in Grafana MCP Server

Published Aug 11, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.1Critical · v3.1
EPSS0.31%24th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-19516CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-19516 is a server-side request forgery vulnerability affecting Grafana MCP Server and mcp-grafana through version 1.0.0. A caller-supplied X-Grafana-URL header controls the outbound destination, while the grafana_api_request tool permits caller-controlled HTTP methods, paths, and bodies. Destinations are not restricted to the configured Grafana instance, allowing requests to internal, loopback, and link-local services and disclosure of their responses. The earlier fix for CVE-2026-15583 prevented forwarding the configured Grafana service-account token to unintended destinations but did not eliminate the unrestricted requests.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation exposes otherwise inaccessible services and sensitive data reachable from the MCP server's network position. In certain deployments, attackers can retrieve cloud credentials from AWS IMDSv2 using the tool's method-capable request interface. Metadata access depends on deployment-specific reachability. This vulnerability does not itself disclose the configured Grafana service-account token. A separate session-validation weakness can enable unauthenticated exploitation when chained with the SSRF.

Mitigation

If you can’t patch tonight, do this now.

Enforce a strict outbound destination allowlist permitting only the intended Grafana instance, and block access to private, loopback, link-local, and cloud-metadata destinations by default. Require inbound authentication for remote MCP access and minimize Grafana service-account permissions. Authentication and reduced account permissions are defense-in-depth measures, not substitutes for restricting outbound destinations.

Remediation

Patch, then assume compromise.

Upgrade Grafana MCP Server or mcp-grafana to version 1.1.0, which fixes the SSRF by restricting outbound destinations to the intended configured Grafana instance. The earlier CVE-2026-15583 fix alone is insufficient. For remotely accessible deployments, also configure the optional bearer-token authentication introduced in version 1.1.0.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
FAQ

Frequently asked questions

Is CVE-2026-19516 exploited in the wild?
As of Oct 14, 2026, Mallory has no reports of CVE-2026-19516 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19516?
As of Oct 14, 2026, Mallory has found no public exploit for CVE-2026-19516.
Is there a patch for CVE-2026-19516?
Upgrade Grafana MCP Server or mcp-grafana to version 1.1.0, which fixes the SSRF by restricting outbound destinations to the intended configured Grafana instance. The earlier CVE-2026-15583 fix alone is insufficient.
How severe is CVE-2026-19516?
CVE-2026-19516 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.31% (24th percentile) as of Oct 14, 2026.
Activity feed

Recent activity

20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity9Community discussion across Reddit, Mastodon, and other social sources.