Cyber Resilience

CVE-2026-55967

Wolfssl 4.8.0 – 5.9.2

Published
25 June 2026
Modified
26 June 2026
Patch / advisory
View advisory
CVSS Score v4 2.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0011 2th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-55967 is a low-severity Reusing a Nonce, Key Pair in Encryption (CWE-323) vulnerability in Wolfssl Wolfssl. Its CVSS base score is 2.0 (Low).

Operationally, ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly rejected by the streaming APIs, allowing counter wrap, keystream reuse, and consequent plaintext recovery.

CWE(s)
CWE-323

Related Threats

CVEs Like This One

CVE-2026-5503Same product: Wolfssl Wolfssl
CVE-2026-10512Same product: Wolfssl Wolfssl
CVE-2024-1544Same product: Wolfssl Wolfssl
CVE-2026-55960Same product: Wolfssl Wolfssl
CVE-2026-6329Same product: Wolfssl Wolfssl
CVE-2026-11703Same product: Wolfssl Wolfssl
CVE-2026-6679Same product: Wolfssl Wolfssl
CVE-2025-7394Same product: Wolfssl Wolfssl
CVE-2026-6092Same product: Wolfssl Wolfssl
CVE-2024-1543Same product: Wolfssl Wolfssl

Affected Assets

wolfssl
wolfssl
4.8.0 — 5.9.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.8.3
  • V11.3.4

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover nonce reuse through static analysis, fuzzing, or known-answer tests.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include correct use of cryptographic primitives such as unique nonces per key.

SC-13 Cryptographic Protection partial match

Selecting and implementing appropriate cryptographic algorithms and modes reduces nonce-reuse exposure.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent nonce/key reuse errors in cryptographic implementations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandates proper cryptographic key and nonce management, directly preventing nonce/key-pair reuse.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect nonce reuse, yet the control addresses many other issues beyond this CWE.

A.8.28 Secure coding partial match
prevents

Secure-coding rules can require unique nonces, but the control is broader than this single weakness.

References