dbcve.org
CWE-610Weakness · CWE-610

CVE-2026-15583

HIGH · 8.6 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A confused-deputy flaw in Grafana MCP Server allows an unauthenticated remote attacker to exfiltrate the server's environment-configured Grafana service-account token by supplying a crafted X-Grafana-URL request header. This also enables SSRF against arbitrary internal services, including cloud metadata endpoints.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Grafana MCP Server suffers from a confused-deputy vulnerability where an unauthenticated attacker can supply a malicious X-Grafana-URL header to trick the server into making requests to attacker-controlled URLs. Since the server uses a Grafana service-account token from its environment for authentication, attackers can capture this token by pointing the header to their controlled endpoint. The same mechanism enables SSRF attacks against internal services and cloud metadata endpoints.

MitigationImplement strict allowlist validation on the X-Grafana-URL header to only permit the configured Grafana instance URL, apply network segmentation to block outbound connections from the server to internal services and metadata endpoints, and rotate any potentially exposed service-account tokens.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Grafana MCP Server is installed
    Check for the grafana-mcp-server binary or package on the system. Common locations include /usr/local/bin/, /usr/bin/, or via package managers (npm list @grafana/mcp-server, pip list, docker ps).
    Affected if The Grafana MCP Server binary or container is present on the system.
  2. Determine the installed version of Grafana MCP Server
    Run the version command for the installed package: grafana-mcp-server --version, npm list @grafana/mcp-server version, or check the Docker image tag. Compare the version to any published fixed versions from Grafana labs.
    Affected if The installed version matches the vulnerable version range (check Grafana security advisories for specific affected versions).
  3. Verify X-Grafana-URL header acceptance
    Inspect the server configuration or source code to confirm the X-Grafana-URL header is processed and used to construct outbound requests. Look for code that uses this header value in HTTP requests without validation.
    Affected if The server accepts and uses the X-Grafana-URL header to direct outbound HTTP requests without strict allowlist validation.
  4. Check for service-account token in environment
    Review the environment variables where Grafana MCP Server runs: look for GRAFANA_TOKEN, GRAFANA_SERVICE_ACCOUNT_TOKEN, or similar variables containing Grafana authentication credentials.
    Affected if A Grafana service-account token is present in the server's environment variables or configuration files.
  5. Assess network accessibility from the server
    Review firewall rules, network policies, or iptables/iptables-save output to determine if the server can make arbitrary outbound HTTP/HTTPS connections to internal services and cloud metadata endpoints (e.g., 169.254.169.254).
    Affected if The server has unrestricted outbound network access allowing connections to arbitrary URLs including internal infrastructure.

You are affected if Grafana MCP Server is running with a service-account token in its environment, accepts the X-Grafana-URL header without validation, and has outbound network access that permits connections to attacker-controlled or internal endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist validation on the X-Grafana-URL header to only permit the configured Grafana instance URL, apply network segmentation to block outbound connections from the server to internal services and metadata endpoints, and rotate any potentially exposed service-account tokens.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15583 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data