CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in grafana grafana. EPSS 17% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/grafana/grafana 1.9.2-0.20251106142618-ca5d89812015, 12.0.7, 12.1.4.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hgithub.com/grafana/grafana (Go): fixed in 12.0.7, 12.1.4, 12.2.2, 1.9.2-0.20251106142618-ca5d89812015Explain CVE-2025-41115 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-41115?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-41115?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-2025-41115 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Grafana Enterprise | from 12.0.0 before 12.2.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-w62r-7c53-fmc5 | Go | github.com/grafana/grafana | >=12.0.0 <12.0.7 | 12.0.7 |
| GHSA-w62r-7c53-fmc5 | Go | github.com/grafana/grafana | >=12.1.0 <12.1.4 | 12.1.4 |
| GHSA-w62r-7c53-fmc5 | Go | github.com/grafana/grafana | >=12.2.0 <12.2.2 | 12.2.2 |
| GHSA-w62r-7c53-fmc5 | Go | github.com/grafana/grafana | >=1.9.2-0.20250310110405-e6fdb746f235 <1.9.2-0.20251106142618-ca5d89812015 | 1.9.2-0.20251106142618-ca5d89812015 |
| GO-2025-4153 | Go | github.com/grafana/grafana | >=1.9.2-0.20250310110405-e6fdb746f235 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20251209T172047-150000.1.127.1 | SUSE-SU-2025:4395-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20251209T172047-150000.1.127.1 | SUSE-SU-2025:4395-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Critical.
No Red Hat products or offerings are affected by this vulnerability. As the version of grafana (9.x/10.x) shipped in this version of Red Hat Enterprise Linux is not vulnerable to this CVE. The vulnerable versions listed in the CVE posting are >= 12.0.x which are all not in Red Hat Enterprise Linux.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Multicluster Global Hub | multicluster-globalhub/multicluster-globalhub-grafana-rhel9 | Not affected | |
| Red Hat Advanced Cluster Management for Kubernetes 2 | rhacm2/acm-grafana-rhel9 | Not affected | |
| Red Hat Enterprise Linux 10 | grafana | Not affected | |
| Red Hat Enterprise Linux 8 | grafana | Not affected | |
| Red Hat Enterprise Linux 9 | grafana | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-41115.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.