Skip to main content
CVE-2025-3454VulnerabilityPublished

CVE-2025-3454: Grafana · CWE-285

Affects GrafanaSource CVE Database V5

0

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Grafana GrafanaAffected
  • =11.6.0
  • =11.5.0
  • =11.4.0
  • =11.3.0
  • =11.2.0
  • =10.4.0
Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Immediately audit Grafana installations to identify affected versions (10.4.0 through 11.6.0) and prioritize upgrades to patched versions once available. 2) Until patches are released, restrict access to Grafana instances to trusted networks and users, employing network segmentation and firewall rules to limit exposure. 3) Review and tighten datasource permissions, ensuring that users have the minimal necessary privileges and that route-specific permissions are correctly configured. 4) Implement web application firewalls (WAFs) or reverse proxies capable of normalizing URL paths to prevent exploitation via URL path manipulation (extra slash). 5) Monitor Grafana logs for unusual access patterns or attempts to exploit URL path manipulations. 6) Coordinate with Grafana vendors or community channels to obtain patches or workarounds as soon as they become available. 7) Educate administrators and users about the vulnerability to avoid inadvertent exposure or misconfiguration.

Description

This vulnerability in Grafana's datasource proxy API allows authorization checks to be bypassed by adding an extra slash character in the URL path. Users with minimal permissions could gain unauthorized read access to GET endpoints in Alertmanager and Prometheus datasources. The issue primarily affects datasources that implement route-specific permissions, including Alertmanager and certain Prometheus-based datasources.

References

Community reviews

Loading reviews…