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.
References
| Link | Resource |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/10702 | Issue Tracking Patch |
| https://www.wolfssl.com/docs/security-vulnerabilities/ | Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-06-25 18:16
Updated : 2026-06-26 16:50
NVD link : CVE-2026-55961
Mitre link : CVE-2026-55961
CVE.ORG link : CVE-2026-55961
JSON object : View
Products Affected
wolfssl
- wolfssl
CWE
CWE-347
Improper Verification of Cryptographic Signature
