Cross-Site Scripting (XSS) in github.com/prometheus/prometheus (CVE-2026-44903)
Summary
Cross-site scripting in github.com/prometheus/prometheus (CVE-2026-44903). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.311.3 or later.
Original description
The description as published by the source.
Prometheus is an open-source monitoring system and time series database. From 2.49.0 to before 3.5.3 and 3.11.3, in the Prometheus server's legacy web UI (enabled via the command-line flag --enable-feature=old-ui), the histogram heatmap chart view does not escape le label values when inserting them into the HTML for use as axis tick mark labels. An attacker who can inject crafted metrics can execute JavaScript in the browser of any Prometheus user who views the metric in the heatmap chart UI. This vulnerability is fixed in 3.5.3 and 3.11.3.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44903 has been found in github.com/prometheus/prometheus.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade github.com/prometheus/prometheus to 0.311.3 or later.
If unsure, ask your IT team or search "github.com/prometheus/prometheus CVE-2026-44903" on the vendor's site.
CVE-2026-44903 (github.com/prometheus/prometheus) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.311.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in github.com/prometheus/prometheus.
Check the vendor advisory for the affected versions of github.com/prometheus/prometheus.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.311.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/prometheus/prometheus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/prometheus/prometheus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/prometheus/prometheusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/prometheus/prometheus to 0.311.3ステージング環境で 0.311.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44903 prometheus
- Ubuntu UBUNTU-CVE-2026-44903 prometheus
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com