CVE-2026-40179

Workarounds

• If using the remote write receiver (--web.enable-remote-write-receiver), ensure it is not exposed to untrusted sources.
• If using the OTLP receiver (--web.enable-otlp-receiver), ensure it is not exposed to untrusted sources.
• Ensure scrape targets are trusted and not under attacker control.
• Do not enable admin / mutating API endpoints (e.g. --web.enable-admin-api or web.enable-lifecycle) in cases where you cannot prevent untrusted data from being ingested.
• Users should avoid clicking untrusted links, especially those containing functions such as label_replace, as they may generate poisoned label names and values.

Acknowledgements

Thanks to @gladiator9797 (Duc Anh Nguyen from TinyxLab) for reporting this.

Stored cross-site scripting (XSS) via crafted metric names in the Prometheus web UI:

• Old React UI + New Mantine UI: When a user hovers over a chart tooltip on the Graph page, metric names containing HTML/JavaScript are injected into innerHTML without escaping, causing arbitrary script execution in the user's browser.
• Old React UI only: When a user opens the Metric Explorer (globe icon next to the PromQL expression input field), and a metric name containing HTML/JavaScript is rendered in the fuzzy search results, it is injected into innerHTML without escaping, causing arbitrary script execution in the user's browser.
• Old React UI only: When a user views a heatmap chart and hovers over a cell, the le label values of the underlying histogram buckets are interpolated into innerHTML without escaping. While le is conventionally a numeric bucket boundary, Prometheus does not enforce this, arbitrary UTF-8 strings are accepted as label values, allowing script injection via a crafted scrape target or remote write.

With Prometheus v3.x defaulting to UTF-8 metric and label name validation, characters like <, >, and " are now valid in metric names and labels, making this exploitable.

An attacker who can inject metrics (via a compromised scrape target, remote write, or OTLP receiver endpoint) can execute JavaScript in the browser of any Prometheus user who views the metric in the Graph UI. From the XSS context, an attacker could for example:

• Read /api/v1/status/config to extract sensitive configuration (although credentials / secrets are redacted by the server)
• Call /-/quit to shut down Prometheus (only if --web.enable-lifecycle is set)
• Call /api/v1/admin/tsdb/delete_series to delete data (only if --web.enable-admin-api is set)
• Exfiltrate metric data to an external server

Both the new Mantine UI and the old React UI are affected. The vulnerable code paths are:

• web/ui/mantine-ui/src/pages/query/uPlotChartHelpers.ts, tooltip innerHTML with unescaped labels.__name__
• web/ui/react-app/src/pages/graph/GraphHelpers.ts, tooltip content with unescaped labels.__name__
• web/ui/react-app/src/pages/graph/MetricsExplorer.tsx, fuzzy search results rendered via dangerouslySetInnerHTML without sanitization
• web/ui/react-app/src/vendor/flot/jquery.flot.heatmap.js, heatmap tooltip with unescaped label values

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-40179 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.311.2-0.20260410083055-07c6232d159b); upgrading removes the vulnerable code path.

Kodem intelligence

A patch has been published in Prometheus 3.5.2 LTS and Prometheus 3.11.2. The fix applies escapeHTML() to all user-controlled values (metric names and label values) before inserting them into innerHTML. This advisory will be updated with the patched version once released.

1. What is CVE-2026-40179? CVE-2026-40179 is a medium-severity cross-site scripting (XSS) vulnerability in github.com/prometheus/prometheus (go), affecting versions >= 3.0.0, <= 3.5.1. It is fixed in 0.311.2-0.20260410083055-07c6232d159b. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-40179? CVE-2026-40179 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/prometheus/prometheus are affected by CVE-2026-40179? github.com/prometheus/prometheus (go) versions >= 3.0.0, <= 3.5.1 is affected.
4. Is there a fix for CVE-2026-40179? Yes. CVE-2026-40179 is fixed in 0.311.2-0.20260410083055-07c6232d159b. Upgrade to this version or later.
5. Is CVE-2026-40179 exploitable, and should I be worried? Whether CVE-2026-40179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40179 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40179? Upgrade github.com/prometheus/prometheus to 0.311.2-0.20260410083055-07c6232d159b or later.