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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| wolfSSL | wolfSSL | >= 3.15.7, <= 5.9.1 |
References
- https://github.com/wolfSSL/wolfssl/pull/10702Issue Tracking, Patch
- https://www.wolfssl.com/docs/security-vulnerabilities/Vendor Advisory
Timeline
- Published
- Jun 25, 2026
- Last modified
- Jun 26, 2026
- NVD status
- Analyzed