Signature bypass via empty PKCS7 signerInfos
Published Jun 25, 2026 · Updated Jun 25, 2026
Improper signature verification in wolfSSL 3.15.7 through 5.9.1 allows attackers to pass unsigned content as verified via degenerate PKCS#7 bundles. wolfSSL_PKCS7_verify() treats empty signerInfos as successful signed-data verification without authenticating any content. Reachability requires an OpenSSL compatibility build whose application passes attacker-controlled bundles to PKCS7_verify(); the result is acceptance of unauthenticated content.
Summary
What happened
Improper signature verification in wolfSSL 3.15.7 through 5.9.1 allows attackers to pass unsigned content as verified via degenerate PKCS#7 bundles. wolfSSL_PKCS7_verify() treats empty signerInfos as successful signed-data verification without authenticating any content. Reachability requires an OpenSSL compatibility build whose application passes attacker-controlled bundles to PKCS7_verify(); the result is acceptance of unauthenticated content.
The record
- CVE
- CVE-2026-55961
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-347, T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.15.7 <=5.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo