CVSS 3.1
6.3 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:NCVE-2026-106472 Server-side request forgery in the Prometheus data source resource API
Medium (6.3) in grafana. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
Grafana's Prometheus data source passes the resource path supplied by the caller to the configured Prometheus server without restricting it to the supported API endpoints [missing path allowlist]. A user with permission to query the data source can read responses from other endpoints on that server using the data source's credentials.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-918 Server-Side Request Forgery (SSRF)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GRAFANA (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-106472 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106472?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106472?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106472 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-106472)
HTML:
<a href="https://cve.bz/cve/CVE-2026-106472"><img src="https://cve.bz/cve/badge/CVE-2026-106472.svg" alt="CVE-2026-106472"></a>
Affected
- grafana:grafana enterprise
- grafana:grafana oss
- grafana:prometheus datasource
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Grafana OSS | from 9.1.0 through 11.6.16 |
| Grafana OSS | from 12.0.0 through 12.2.10 |
| Grafana OSS | from 12.3.0 through 12.3.11 |
| Grafana OSS | from 12.4.0 before 12.4.15 |
| Grafana OSS | from 13.0.0 before 13.0.13 |
| Grafana OSS | from 13.1.0 before 13.1.10 |
| Grafana Enterprise | from 9.1.0 through 11.6.16 |
| Grafana Enterprise | from 12.0.0 through 12.2.10 |
| Grafana Enterprise | from 12.3.0 through 12.3.11 |
| Grafana Enterprise | from 12.4.0 before 12.4.15 |
| Grafana Enterprise | from 13.0.0 before 13.0.13 |
| Grafana Enterprise | from 13.1.0 before 13.1.10 |
| Grafana Prometheus Datasource | from 13.1.1 through 13.1.9 |
| Grafana Prometheus Datasource | from 13.2.0 before 13.2.6 |
Attack patterns (CAPEC)
- CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.