CVE-2026-40179

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-23123 (ENISA EUVD) · GHSA-vffh-x6r8-xx99 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Prometheus is an open-source monitoring system and time series database. Versions 3.0 through 3.5.1 and 3.6.0 through 3.11.1 have stored cross-site scripting vulnerabilities in multiple components of the Prometheus web UI where metric names and label values are injected into innerHTML without escaping. In both the Mantine UI and old React UI, chart tooltips on the Graph page render metric names containing HTML/JavaScript without sanitization. In the old React UI, the Metric Explorer fuzzy search results use dangerouslySetInnerHTML without escaping, and heatmap cell tooltips interpolate le label values without sanitization. With Prometheus v3.x defaulting to UTF-8 metric and label name validation, characters like <, >, and " are now valid in metric names and labels. An attacker who can inject metrics via a compromised scrape target, remote write, or OTLP receiver endpoint can execute arbitrary JavaScript in the browser of any Prometheus user who views the metric in the Graph UI, potentially enabling configuration exfiltration, data deletion, or Prometheus shutdown depending on enabled flags. This issue has been fixed in versions 3.5.2 and 3.11.2. If developers are unable to immediately update, the following workarounds are recommended: ensure that the remote write receiver (--web.enable-remote-write-receiver) and the OTLP receiver (--web.enable-otlp-receiver) are not exposed to untrusted sources; verify that all scrape targets are trusted and not under attacker control; avoid enabling admin or mutating API endpoints (e.g., --web.enable-admin-api or --web.enable-lifecycle) in environments where untrusted data may be ingested; and refrain from clicking untrusted links, particularly those containing functions such as label_replace, as they may generate poisoned label names and values.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 15, 2026

Last Modified

April 22, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

Stored XSS via metric names and label values in Prometheus web UI tooltips and metrics explorer · Advisory · prometheus/prometheus · GitHub

Affected: v2.7.2

https://github.com/prometheus/prometheus/security/advisories/GHSA-vffh-x6r8-xx99
GitHub pull request

UI: Fix stored XSS via unescaped metric names and labels

Fix merged in prometheus/prometheus PR #18506 on 2026-04-10 — awaiting tagged release

https://github.com/prometheus/prometheus/pull/18506
GitHub commit

commit 07c6232d159b (prometheus/prometheus)

Fix landed in prometheus/prometheus commit 07c6232d159b — awaiting tagged release

https://github.com/prometheus/prometheus/commit/07c6232d159bfb474a077788be184d87adcfac3c

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/prometheus/prometheus—
  • 3.0.0 up to 3.5.2: fixed in 3.5.2
  • 3.6.0 up to 3.11.2: fixed in 3.11.2
  • every version up to 0.311.2-0.20260410083055-07c6232d159b: fixed in 0.311.2-0.20260410083055-07c6232d159b
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-25 14:31 UTCEG score recompute
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-23 02:33 UTCEG score recompute
  10. 2026-10-23 02:33 UTCVendor advisory
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-18 03:43 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-12 16:09 UTCEG score recompute
  24. 2026-10-11 19:52 UTCEG score recompute
  25. 2026-10-11 17:05 UTCEG score recompute
Show 74 more
  1. 2026-10-11 14:31 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-10 19:33 UTCOSV refresh
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-09-21 06:49 UTCOSV refresh
  18. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-09-02 04:58 UTCOSV refresh
  35. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-08-16 06:37 UTCEG score recompute
  51. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-14 04:43 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-12 18:52 UTCEG score recompute
  56. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-08-11 04:54 UTCEG score recompute
  59. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-08-10 04:27 UTCEG score recompute
  61. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  62. 2026-08-09 03:59 UTCEG score recompute
  63. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  64. 2026-08-07 13:25 UTCEG score recompute
  65. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-08-05 23:22 UTCEG score recompute
  67. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  68. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-08-03 21:34 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-08-02 13:13 UTCEG score recompute
  73. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  74. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile

Frequently asked(5)

What is CVE-2026-40179?
CVE-2026-40179 is a medium-severity vulnerability; its CVE record was published on April 15, 2026. Prometheus is an open-source monitoring system and time series database. Versions 3.0 through 3.5.1 and 3.6.0 through 3.11.1 have stored cross-site scripting vulnerabilities in multiple components of the Prometheus web UI where metric names and label values are injected into innerHTML without…
When was the CVE record for CVE-2026-40179 published?
The CVE record for CVE-2026-40179 was published on April 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 22, 2026; the record at its source may have been updated since.
Is CVE-2026-40179 actively exploited?
CVE-2026-40179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40179?
CVE-2026-40179 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-40179?
A fix for CVE-2026-40179 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40179 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40179

Explore →

Is Your Infrastructure Affected by CVE-2026-40179?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.