Vulnerability Description
wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 object that contains no signer. Such an object has empty signerInfos, so the underlying signed-data verification succeeds without authenticating any content. The compatibility-layer verify path now rejects the object when no signer signature has actually been verified, so a PKCS#7 carrying no valid signature is no longer reported as verified. This is enforced regardless of the PKCS7_NOVERIFY flag, which only suppresses signer certificate chain validation and was never intended to waive the requirement that a signature exist. Only affects OpenSSL compatibility builds that call the PKCS7_verify() compatibility API on potentially degenerate PKCS#7 bundles.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Wolfssl | Wolfssl | >= 3.15.7, < 5.9.2 |
Related Weaknesses (CWE)
References
- https://github.com/wolfSSL/wolfssl/pull/10702Issue TrackingPatch
- https://www.wolfssl.com/docs/security-vulnerabilities/Vendor Advisory
FAQ
What is CVE-2026-55961?
CVE-2026-55961 is a vulnerability with a CVSS score of 7.5 (HIGH). wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 object that contains no signer. Such an object has empty signerInfos, so the underlying signed-data verification succeeds ...
How severe is CVE-2026-55961?
CVE-2026-55961 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-55961?
Check the references section above for vendor advisories and patch information. Affected products include: Wolfssl Wolfssl.