https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 23:09:22 +0000 https://db.gcve.eu/vuln/ghsa-vffh-x6r8-xx99 <p><strong>Affected:</strong> Go: github.com/prometheus/prometheus</p> <p>### Impact</p> <p>Stored cross-site scripting (XSS) via crafted metric names in the Prometheus web UI:</p> <p>* **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&#39;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&#39;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.</p> <p>With Prometheus v3.x defaulting to UTF-8 metric and label name validation, characters like `&lt;`, `&gt;`, and `&#34;` are now valid in metric names and labels, making this exploitable.</p> <p>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 exampl…</p> <p><strong>Affected:</strong> Go: github.com/prometheus/prometheus</p> <p>### Impact</p> <p>Stored cross-site scripting (XSS) via crafted metric names in the Prometheus web UI:</p> <p>* **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&#39;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&#39;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.</p> <p>With Prometheus v3.x defaulting to UTF-8 metric and label name validation, characters like `&lt;`, `&gt;`, and `&#34;` are now valid in metric names and labels, making this exploitable.</p> <p>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 exampl…</p> https://db.gcve.eu/vuln/ghsa-vffh-x6r8-xx99