CVE-2026-42151

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the client_secret field in the Azure AD remote write OAuth configuration (storage/remote/azuread) was typed as string instead of Secret. Prometheus redacts fields of type Secret when serving the configuration via the /-/config HTTP API endpoint. Because the field was a plain string, the Azure OAuth client secret was exposed in plaintext to any user or process with access to that endpoint. This issue has been patched in versions 3.5.3 and 3.11.3.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 23, 2026

Advisory Details (5)

Auto-updated May 4, 2026
Patch available. Sources: github.
github Patch Available

Prometheus Azure AD remote write OAuth client secret exposed via config API · Advisory · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/security/advisories/GHSA-wg65-39gg-5wfj
generic

Release 3.5.3 / 2026-04-27 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/releases/tag/v3.5.3
generic

Release 3.11.3 / 2026-04-27 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/releases/tag/v3.11.3
generic

remote/azuread: use Secret type for OAuth client_secret by roidelapluie · Pull Request #18590 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/pull/18590
generic

remote/azuread: use Secret type for OAuth client_secret by roidelapluie · Pull Request #18587 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/pull/18587

Vendor Advisories for CVE-2026-42151(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatopenshift4/ose-cluster-monitoring-rhel9-operator:17841250782026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhtas/updatetree-rhel9:17839688612026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatrhtas/createtree-rhel9:17839688612026-07-16redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17840606812026-07-16redhat
redhatrhem/flightctl-worker-rhel10:17841949712026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatrhtas/trillian-logsigner-rhel9:17839688612026-07-16redhat
redhatrhem/flightctl-worker-rhel9:17841277752026-07-15redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat
redhatrhtas/trillian-logsigner-rhel9:17833297932026-07-09redhat
redhatrhtas/createtree-rhel9:17833297932026-07-09redhat
redhatconforma-cli-stack-v1-4-1.4.22026-07-09redhat
redhatrhtas/updatetree-rhel9:17833297932026-07-09redhat
redhatrhem/flightctl-worker-rhel9:17835024452026-07-08redhat
redhatflightctl-0:1.0.3-1.el9em2026-07-08redhat
redhatopentelemetry-collector-0:0.152.1-1.el10_22026-07-01redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_82026-07-01redhat
redhatopentelemetry-collector-contrib-main-0.153.0-1.hum12026-06-12redhat
redhatopentelemetry-collector-main-0.153.0-1.hum12026-06-11redhat
redhatjaeger-main-2.19.0-1.hum12026-06-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/prometheus/prometheus—0.311.3—

Weakness Classification(3)

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

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 113 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42151?
CVE-2026-42151 is a high vulnerability published on May 4, 2026. Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the client_secret field in the Azure AD remote write OAuth configuration (storage/remote/azuread) was typed as string instead of Secret. Prometheus redacts fields of type Secret when serving…
When was CVE-2026-42151 disclosed?
CVE-2026-42151 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42151 actively exploited?
CVE-2026-42151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.2% of all scored CVEs.
What is the CVSS score of CVE-2026-42151?
CVE-2026-42151 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42151?

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

Start Free Scan →Browse All CVEs