CVE-2026-31837

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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
Trending — 3 sources updated 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.

Istio is an open platform to connect, manage, and secure microservices. Prior to 1.29.1, 1.28.5, and 1.27.8, a user of Istio is impacted if the JWKS resolver becomes unavailable or the fetch fails, exposing hardcoded defaults regardless of use of the RequestAuthentication resource. This vulnerability is fixed in 1.29.1, 1.28.5, and 1.27.8.

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
31%
KEV
Not listed

Published

March 10, 2026

Last Modified

July 20, 2026

Advisory Details (8)

Auto-updated Jul 7, 2026
Patch available. Sources: github, redhat.
redhat
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31837.json
redhat

2446344 – (CVE-2026-31837) CVE-2026-31837 istio: Istio: Information disclosure and authentication bypass via JWKS resolver unavailability

https://bugzilla.redhat.com/show_bug.cgi?id=2446344
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-31837
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5952
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5950
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5948
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10184
github Patch Available

JWKS Resolver Failure May Expose Hardcoded Default Keys · Advisory · istio/istio · GitHub

https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c

Vendor Advisories for CVE-2026-31837(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-kserve-router-rhel9:17763431212026-04-23redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17740688552026-03-26redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17742441362026-03-26redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17741149032026-03-26redhat

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 58× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31837?
CVE-2026-31837 is a high vulnerability published on March 10, 2026. Istio is an open platform to connect, manage, and secure microservices. Prior to 1.29.1, 1.28.5, and 1.27.8, a user of Istio is impacted if the JWKS resolver becomes unavailable or the fetch fails, exposing hardcoded defaults regardless of use of the RequestAuthentication resource. This…
When was CVE-2026-31837 disclosed?
CVE-2026-31837 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31837 actively exploited?
CVE-2026-31837 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 68.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31837?
CVE-2026-31837 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31837, 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

Explore the affected products and dependency analysis for CVE-2026-31837

Explore →

Is Your Infrastructure Affected by CVE-2026-31837?

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

Start Free Scan →Browse All CVEs