Skip to main content
VulnerabilityPublished Updated

CVE-2025-41117: github.com/grafana/grafana · Grafana has a Cross-site Scripting issue

Affects github.com/grafana/grafanaSource GCVE Database

0
Authoritative record:CVE-2025-41117· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : upgrade to 12.2.5 when convenient.

Data as of 27 Oct 2026, 01:27 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 12.2.5, 12.3.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2026

  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 26 Oct 2026.

What to do

Upgrade github.com/grafana/grafana to 12.2.5; github.com/grafana/grafana to 12.3.3.

Affected software

ProductAffectedFixed in
Gogithub.com/grafana/grafanaAffected
  • >=12.2.0 <12.2.5
Fixed in
  • 12.2.5
Gogithub.com/grafana/grafanaAffected
  • >=12.3.0 <12.3.3
Fixed in
  • 12.3.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading to Grafana versions 12.2.5 or 12.3.3 or later. No other mitigation or workaround is indicated. Users should update affected Grafana instances promptly to remediate this vulnerability.

Description

Grafana versions 12.2.0 through before 12.2.5 and 12.3.0 through before 12.3.3 have a cross-site scripting (XSS) vulnerability in the Explore Traces view. This occurs because stack traces can be rendered as raw HTML, allowing malicious JavaScript injection if crafted input is entered into the stack trace field. The issue affects only datasources using the Jaeger HTTP API; Jaeger gRPC and Tempo datasources are not impacted. A fix is available in versions 12.2.5 and 12.3.3.

References

Community reviews

Loading reviews…