← Back
CVE-2026-44903
medium
CVSS 6.1
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. Exploitable via ``label_replace``. Mitigation: upgrade to `2.7.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44903** has been found in github.com/prometheus/prometheus.
Attackers can target a specific entry point like ``label_replace`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade github.com/prometheus/prometheus to **2.7.2** 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
Attack surface: `label_replace`
Patched: `2.7.2` — 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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in github.com/prometheus/prometheus. Attackers reach the vulnerable code path via ``label_replace`` without authentication.
📍 Affected scope
github.com/prometheus/prometheus — . Attack surface: `label_replace`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.7.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/prometheus/prometheus to 2.7.2ステージング環境で 2.7.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/prometheus/prometheus
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.311.3"}]}]
Bitnami
prometheus
[{"type":"SEMVER","events":[{"introduced":"2.49.0"},{"fixed":"3.5.3"},{"introduced":"3.6.0"},{"fixed":"3.11.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44903
- package https://github.com/prometheus/prometheus
- web https://github.com/prometheus/prometheus/security/advisories/GHSA-fw8g-cg8f-9j28
- web https://github.com/prometheus/prometheus/commit/38f23b9075ced1de2b82d2dad8b2bebb1ecd5b7d
- web https://github.com/advisories/GHSA-fw8g-cg8f-9j28