CVE-2026-42151

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% 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, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
24.5%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 6, 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(6)

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

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.

Data Freshness Timeline

(refreshed 8× in last 7d / 65× 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 115 total refreshes for this CVE.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
Show 75 more
  1. 2026-06-16 17:52 UTCEPSS rescore
  2. 2026-06-15 17:49 UTCEPSS rescore
  3. 2026-06-15 05:51 UTCEG score recompute
  4. 2026-06-15 05:51 UTCVendor advisory
  5. 2026-06-14 18:58 UTCEG score recompute
  6. 2026-06-14 18:58 UTCVendor advisory
  7. 2026-06-14 08:06 UTCEG score recompute
  8. 2026-06-14 08:06 UTCVendor advisory
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 06:42 UTCEG score recompute
  13. 2026-06-12 06:42 UTCVendor advisory
  14. 2026-06-11 19:50 UTCEG score recompute
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-11 08:57 UTCEG score recompute
  17. 2026-06-11 08:57 UTCVendor advisory
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-10 20:58 UTCEG score recompute
  20. 2026-06-10 20:58 UTCVendor advisory
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-10 10:05 UTCEG score recompute
  24. 2026-06-10 10:05 UTCVendor advisory
  25. 2026-06-09 23:13 UTCEG score recompute
  26. 2026-06-09 23:13 UTCVendor advisory
  27. 2026-06-09 09:40 UTCEG score recompute
  28. 2026-06-09 09:40 UTCVendor advisory
  29. 2026-06-08 22:36 UTCEG score recompute
  30. 2026-06-08 22:36 UTCVendor advisory
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-08 14:17 UTCEPSS rescore
  33. 2026-06-08 06:03 UTCEG score recompute
  34. 2026-06-08 06:03 UTCVendor advisory
  35. 2026-06-07 19:11 UTCEG score recompute
  36. 2026-06-07 19:11 UTCVendor advisory
  37. 2026-06-07 15:25 UTCEPSS rescore
  38. 2026-06-07 15:25 UTCEPSS rescore
  39. 2026-06-07 08:18 UTCEG score recompute
  40. 2026-06-07 08:18 UTCVendor advisory
  41. 2026-06-06 21:26 UTCEG score recompute
  42. 2026-06-06 21:26 UTCVendor advisory
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 10:10 UTCEG score recompute
  46. 2026-06-06 10:10 UTCVendor advisory
  47. 2026-06-05 23:07 UTCEG score recompute
  48. 2026-06-05 23:07 UTCVendor advisory
  49. 2026-06-05 22:47 UTCEPSS rescore
  50. 2026-06-05 12:15 UTCEG score recompute
  51. 2026-06-05 12:15 UTCVendor advisory
  52. 2026-06-05 01:23 UTCEG score recompute
  53. 2026-06-05 01:23 UTCVendor advisory
  54. 2026-06-04 14:30 UTCEG score recompute
  55. 2026-06-04 14:30 UTCVendor advisory
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 03:38 UTCEG score recompute
  59. 2026-06-04 03:38 UTCVendor advisory
  60. 2026-06-03 16:46 UTCEG score recompute
  61. 2026-06-03 16:46 UTCVendor advisory
  62. 2026-06-03 05:53 UTCEG score recompute
  63. 2026-06-02 20:13 UTCEPSS rescore
  64. 2026-06-02 18:53 UTCEG score recompute
  65. 2026-06-02 08:00 UTCEG score recompute
  66. 2026-06-01 20:55 UTCEG score recompute
  67. 2026-06-01 13:52 UTCEPSS rescore
  68. 2026-06-01 13:52 UTCEPSS rescore
  69. 2026-06-01 09:59 UTCEG score recompute
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-31 00:16 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 6, 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 24.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42151?
CVE-2026-42151 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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