dbcve.org
GrafanaApplication

CVE-2025-41117

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 12.2.4 / 12.3.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack traces in Grafana's Explore Traces view can be rendered as raw HTML, and thus inject malicious JavaScript in the browser. This would require malicious JavaScript to be entered into the stack trace field. Only datasources with the Jaeger HTTP API appear to be affected; Jaeger gRPC and Tempo do not appear affected whatsoever.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in Grafana's Explore Traces view where stack traces are rendered as raw HTML without proper sanitization, allowing injection of malicious JavaScript through stack trace fields when using Jaeger HTTP API datasources.

MitigationUpdate Grafana to the patched version. Until then, restrict or disable Jaeger HTTP API datasource usage and review/trust sources of trace data carefully.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 12.2.0, < 12.2.4>= 12.3.0, < 12.3.2= 12.2.4= 12.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Grafana version
    Run `grafana-server -v` or check the version file typically at /usr/share/grafana/version, or look in the Grafana UI under Administration > Stats
    Affected if The installed version falls within 12.2.0 through 12.2.4 or 12.3.0 through 12.3.2
  2. List configured datasources
    Query the Grafana datasources API endpoint (if authenticated as admin): GET /api/datasources or inspect the provisioning files at /etc/grafana/provisioning/datasources/
    Affected if A datasource of type jaeger-http-api or a Jaeger HTTP API datasource is present and enabled
  3. Verify Explore Traces access
    Check user permissions for the Explore feature and trace viewing capabilities via Grafana UI roles or provisioning files under /etc/grafana/provisioning/
    Affected if Users have access to the Explore Traces view and can view traces from the Jaeger HTTP API datasource identified above

If Grafana version is 12.2.0-12.2.4 or 12.3.0-12.3.2 AND a Jaeger HTTP API datasource is configured with trace data accessible to users, the environment is vulnerable to XSS via the Explore Traces view.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.2.4 / 12.3.2 or later
Fixed in 12.2.412.3.2
Interim mitigation

Update Grafana to the patched version. Until then, restrict or disable Jaeger HTTP API datasource usage and review/trust sources of trace data carefully.

Recommended fix High confidence

Grafana 12.2.5 or 12.3.3 (and later stable releases)

  1. 1. Identify the currently installed Grafana version using `grafana --version` or checking the Grafana logs/UI
  2. 2. For Grafana 12.2.x: Upgrade to version 12.2.5 or later
  3. 3. For Grafana 12.3.x: Upgrade to version 12.3.3 or later
  4. 4. If running Grafana Enterprise, ensure the same version upgrade is applied to the enterprise edition
  5. 5. After upgrade, verify the Explore Traces view functions correctly with Jaeger datasources
  6. 6. Test that stack traces in Jaeger traces are now properly escaped rather than rendered as raw HTML
Caveat Minor patch upgrades typically have no breaking changes; however, always review release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grafana Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41117 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data