Skip to content
Web

CVE-2026-19516

9.1
Critical
EPSS 0.24%Aug 11, 2026

SSRF in mcp-grafana allows requests to internal and metadata endpoints

common questions

Is CVE-2026-19516 being exploited?

Not confirmed. CVE-2026-19516 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-19516?

CVE-2026-19516 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19516?

Not known from our data. No patch reference has been recorded for CVE-2026-19516, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-19516 affect?

CVE-2026-19516 affects mcp-grafana, grafana_api_request tool, Grafana integrations using mcp-grafana. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19516?

Apply vendor patch when available; validate/whitelist X-Grafana-URL; restrict outbound access and block metadata endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
mcp-grafanagrafana_api_request toolGrafana integrations using mcp-grafana
impact

Remote SSRF: attacker can make mcp-grafana send HTTP requests to internal/loopback/link-local services and read responses, risking metadata/token exfiltration.

action required

Immediate action required

affected versions
Grafana Grafana MCP Server
  • affected<= 1.0.0
Grafana mcp-grafana
  • affected<= 1.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free