Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-15583: Grafana MCP Server service-account token disclosure and SSRF

Published Jul 15, 2026 · Updated 29 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3.1
EPSS0.53%45th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-15583CWE-918

CVE-2026-15583 is a confused-deputy vulnerability in Grafana MCP Server that allows an unauthenticated remote attacker to redirect outbound requests using a crafted X-Grafana-URL request header. The server can send its environment-configured Grafana service-account token to an attacker-controlled destination, exposing the credential. The vulnerability also enables server-side request forgery against internal services reachable from the server, including cloud metadata endpoints. It has a CVSS v3.1 score of 8.6 and requires neither authentication nor user interaction. The initial fix prevented credential forwarding to unintended destinations but did not restrict outbound destinations; the remaining SSRF issue was subsequently tracked as CVE-2026-19516.

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.

Successful exploitation exposes the configured Grafana service-account token and permits requests to internal services using the MCP server's network access. A stolen token could enable unauthorized Grafana access within the service account's granted permissions. SSRF can expose sensitive internal information, including cloud metadata where reachable. The assigned CVSS vector indicates high confidentiality impact, with no direct integrity or availability impact.

Mitigation

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

Require authentication for remotely accessible Grafana MCP deployments and restrict access to trusted clients. Enforce explicit outbound destination policies that allow only the intended Grafana instance, and block unnecessary access to internal services and cloud metadata endpoints. Apply least-privilege permissions to the configured Grafana service account. These controls reduce exposure but do not replace vendor updates.

Remediation

Patch, then assume compromise.

Apply the vendor security update for CVE-2026-15583. The exact initial fixed-version boundary is uncertain because available version information conflicts on whether version 0.17.1 is affected. Prefer the latest vendor-supported patched release, ensuring it also includes the outbound-destination restrictions for CVE-2026-19516, fixed in version 1.1.0. The initial CVE-2026-15583 fix alone prevents token forwarding but does not eliminate arbitrary-destination SSRF. If token exposure is suspected, revoke and replace the configured service-account token and review its activity.

FAQ

Frequently asked questions

Is CVE-2026-15583 exploited in the wild?
As of Oct 19, 2026, Mallory has no reports of CVE-2026-15583 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-15583?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-15583, the earliest disclosed Sep 26, 2026.
Is there a patch for CVE-2026-15583?
Apply the vendor security update for CVE-2026-15583. The exact initial fixed-version boundary is uncertain because available version information conflicts on whether version 0.17.1 is affected.
How severe is CVE-2026-15583?
CVE-2026-15583 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.53% (45th percentile) as of Oct 19, 2026.
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 activity3Community discussion across Reddit, Mastodon, and other social sources.