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
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

May 4, 2026

Last Modified

September 10, 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(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-prometheus-rhel9:17882066522026-09-08redhat
redhatopenshift4/ose-prometheus-rhel9:17875595772026-09-01redhat
redhatopenshift4/ose-prometheus-rhel9:17875734912026-09-01redhat
redhatrhacm2/thanos-receive-controller-rhel9:17869799872026-08-26redhat
redhatrhacm2/multicluster-observability-rhel9-operator:17876137362026-08-26redhat
redhatrhacm2/rbac-query-proxy-rhel9:17876893802026-08-26redhat
redhatrhacm2/thanos-rhel9:17872297162026-08-26redhat
redhatrhacm2/rbac-query-proxy-rhel9:17872638342026-08-26redhat
redhatrhacm2/rbac-query-proxy-rhel9:17872224812026-08-26redhat
redhatrhacm2/prometheus-rhel9:17869090362026-08-19redhat
redhatopenshift-logging/opa-openshift-rhel9:17866451092026-08-18redhat
redhatrhacm2/prometheus-rhel9:17865479112026-08-12redhat
redhatcompliance/openshift-file-integrity-rhel8-operator:17864394492026-08-12redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_42026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_62026-08-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17854428722026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el10_02026-08-11redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat
redhatopenshift-logging/opa-openshift-rhel9:17854188522026-08-05redhat
redhatrhtas/createtree-rhel9:17853914262026-08-05redhat
redhatopenshift-logging/opa-openshift-rhel9:17847478152026-07-29redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17849066282026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatopenshift4/ose-cluster-monitoring-rhel9-operator:17841250782026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.53.3+ds1-2 ... 3.5.3+ds1-6~exp1 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.53.3+ds1-2 ... 2.53.5+ds1-5 (7 versions)
  • every version up to 3.5.3+ds1-1: fixed in 3.5.3+ds1-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/prometheus/prometheus—
  • 0.45.2 up to 0.311.3: fixed in 0.311.3
—

Weakness Classification(3)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 33× 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 298 total refreshes for this CVE.

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

Related CVEs(same product + 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 on May 4, 2026, with the most recent update on September 10, 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.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42151?
CVE-2026-42151 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42151?
A fix for CVE-2026-42151 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42151 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-42151

Explore →

Is Your Infrastructure Affected by CVE-2026-42151?

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

Book a Demo →Browse All CVEs