CVE-2026-3503: wolfSSL (wolfCrypt) · PRNG
Affects wolfSSL (wolfCrypt)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.9.0 when convenient.
Data as of 1 Nov 2026, 08:20 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.9.0
CVSS:4.0/AV:P/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/U:AmberExploitation evidence
Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade wolfssl to 5.9.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wolfSSL Inc.wolfSSL (wolfCrypt) | Affected
| Fixed in– |
GitHubwolfssl/wolfsslpkg:github/wolfssl/wolfsslOther threats | Affected
| Fixed in– |
GitHubwolfsslpkg:github/wolfsslOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-3503, organizations should first upgrade wolfSSL to a version where this vulnerability is patched once available. In the absence of a patch, implement hardware-level protections against fault injection attacks, such as voltage and clock glitch detection, electromagnetic shielding, and sensor monitoring to detect abnormal conditions. Employ secure boot and runtime integrity checks to detect tampering attempts. Limit physical access to devices, especially in sensitive environments, to reduce the risk of fault injection. Review and harden the implementation of PRNGs and post-quantum cryptographic algorithms to ensure proper seed handling and validation. Conduct thorough security testing including fault injection analysis during development and deployment. Additionally, consider using hardware security modules (HSMs) or trusted execution environments (TEEs) that provide hardened cryptographic operations resistant to physical attacks. Maintain up-to-date threat intelligence and monitor for any emerging exploits targeting this vulnerability.
Description
CVE-2026-3503 is a medium severity vulnerability in wolfSSL's wolfCrypt library version 5.8.2 affecting ARM Cortex-M microcontrollers. The flaw involves incorrect usage of seeds in the pseudo-random number generator (PRNG) within post-quantum cryptographic implementations (ML-KEM and ML-DSA). Physical attackers can induce transient faults to corrupt or redirect seed or pointer values during the Keccak-based expansion process, potentially compromising key material or cryptographic outcomes. Exploitation requires physical access and high attack complexity, with no user interaction needed. This vulnerability impacts confidentiality due to possible key leakage but has limited scope and availability impact. No known exploits are reported in the wild. Organizations using affected wolfSSL versions on ARM Cortex-M devices should prioritize patching or apply hardware-level protections against fault injection attacks.