Quick answers
- Is CVE-2026-5194 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5194 being exploited in the wild.
- How severe is CVE-2026-5194?
- Critical severity, with a CVSS score of 9.1, published 9 April 2026.
- Which products and versions are affected?
- wolfSSL Inc. wolfSSL 3.12.0 to 5.9.1 (excluding 5.9.1).
- Is there a fix for CVE-2026-5194?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-5194 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-5194?
- Check whether you run Wolfssl. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in wolfSSL's signature verification functions due to missing hash/digest size and OID checks. When verifying ECDSA certificates, the library may accept digests that are smaller than required for the relevant key type or smaller than the standard allows. This issue specifically manifests when EdDSA or ML-DSA is also enabled alongside ECDSA/ECC verification. An attacker could exploit this to weaken the security of certificate-based authentication, provided the public CA key is known. The flaw is categorized as Improper Certificate Validation (CWE-295) and was addressed in version 5.9.1.
Affected products
- wolfSSL Inc. wolfSSL 3.12.0 to 5.9.1 (excluding 5.9.1)
Timeline
- 2026-04-09: advisory: Initial disclosure by wolfSSL Inc.
- 2026-04-16: other: NIST completed initial analysis and assigned CVSS scores.
- 2026-05-23: other: Advisory updated with additional research references.