CVE-2026-55961

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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*

History

26 Jun 2026, 16:50

Type Values Removed Values Added
CPE cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*
References () https://github.com/wolfSSL/wolfssl/pull/10702 - () https://github.com/wolfSSL/wolfssl/pull/10702 - Issue Tracking, Patch
References () https://www.wolfssl.com/docs/security-vulnerabilities/ - () https://www.wolfssl.com/docs/security-vulnerabilities/ - Vendor Advisory
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 7.5
First Time Wolfssl wolfssl
Wolfssl

25 Jun 2026, 18:16

Type Values Removed Values Added
New CVE

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