Skip to main content
VulnerabilityPublished Updated

CVE-2026-19516: Grafana MCP Server · Server-Side Request Forgery

Affects Grafana MCP ServerSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 9.1 Critical.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GrafanaGrafana MCP ServerAffected
  • <=1.0.0
Fixed in–
Grafanamcp-grafanaAffected
  • <=1.0.0
Fixed in–

AI-suggested

Until a fix is available, restrict access to the Grafana MCP Server and monitor for suspicious usage of the X-Grafana-URL header. Avoid exposing the service to untrusted networks or users with low privileges.

Description

A caller-supplied X-Grafana-URL request header controls the destination of mcp-grafana's outbound requests, and the grafana_api_request tool lets the caller also choose the HTTP method, path, and body. Because the destination is not restricted to the configured Grafana instance, a caller can direct requests at internal, loopback, and link-local network services (including metadata endpoints) and read the responses, resulting in server-side request forgery. The fix for CVE-2026-15583 prevented the configured service-account token from being sent to unintended destinations but did not restrict the destinations themselves.

References

Community reviews

Loading reviews…