{"id":"CVE-2026-55961","aliases":["ALPINE-CVE-2026-55961","DEBIAN-CVE-2026-55961","EUVD-2026-39491","GHSA-cj56-5c53-9qjf","JLSEC-2026-736","UBUNTU-CVE-2026-55961"],"status":"published","title":"wolfSSL_PKCS7_verify() reports success for degenerate (certs-only) PKCS#7 with no signer","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.","severity":{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00146,"percentile":0.039,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-347"],"published":"2026-06-25T16:51:18Z","modified":"2026-11-03T06:32:58Z","fixes":[{"ecosystem":"Alpine:v3.24","package":"wolfssl","fixed_in":["5.9.2-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"wolfssl","fixed_in":["5.5.4-2+deb12u3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"wolfssl","fixed_in":["5.7.2-0.1+deb13u2"],"sources":["osv"]},{"ecosystem":"Julia","package":"wolfSSL_jll","fixed_in":["5.9.2+0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.24","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.15.7"},{"fixed":"5.9.2-r0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.5.4-2+deb12u3"}]}],"versions":["5.5.4-2","5.5.4-2+deb12u1","5.5.4-2+deb12u2"]},{"source":"osv","ecosystem":"Debian:13","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.7.2-0.1+deb13u2"}]}],"versions":["5.7.2-0.1","5.7.2-0.1+deb13u1"]},{"source":"osv","ecosystem":"Julia","package":"wolfSSL_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.9.2+0"}]}]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.4.8+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.10.2+dfsg-2","3.12.0+dfsg-1","3.12.2+dfsg-1","3.13.0+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.1.0+dfsg-2","4.2.0+dfsg-1","4.2.0+dfsg-2","4.2.0+dfsg-3","4.3.0+dfsg-2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.6.0-3","5.0.0-1","5.1.1-1","5.2.0-1","5.2.0-2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.5.4-2","5.5.4-2.1","5.6.4-2","5.6.6-1.2","5.6.6-1.3","5.6.6-1.3build1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.7.2-0.1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.9.1-0.1","5.9.2-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"wolfssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.7.2-0.1","5.8.2-1.2","5.8.4-1","5.9.1-0.1"]}],"products":[{"vendor":"wolfssl","product":"wolfssl"}],"references":[{"url":"https://github.com/wolfSSL/wolfssl/pull/10702","tags":["patch","Issue Tracking","Patch","fix","web","report"]},{"url":"https://www.wolfssl.com/docs/security-vulnerabilities/","tags":["Vendor Advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55961","tags":["advisory","web"]},{"url":"https://www.wolfssl.com/docs/security-vulnerabilities","tags":["web"]},{"url":"https://github.com/advisories/GHSA-cj56-5c53-9qjf","tags":["web"]},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-55961","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55961.json","tags":["advisory"]},{"url":"https://github.com/wolfSSL/wolfssl","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-55961","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-55961","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-55961","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-55961","title":"wolfSSL_PKCS7_verify() reports success for degenerate (certs-only) PKCS#7 with no signer","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.","status":"published","published":"2026-06-25T16:51:18.157Z","modified":"2026-06-25T17:57:46.226Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:20:11.925815Z"}],"euvd":[{"id":"EUVD-2026-39491","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.","status":"published","published":"2026-06-25T16:51:18Z","modified":"2026-06-25T17:57:46Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T18:20:25.316004Z"}],"ghsa":[{"id":"GHSA-cj56-5c53-9qjf","title":"wolfSSL_PKCS7_verify() returning success for a degenerate (certs-only) PKCS#7 object that...","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.","status":"published","published":"2026-06-25T18:30:41Z","modified":"2026-06-26T18:33:49Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:09:01.878033Z"}],"nvd":[{"id":"CVE-2026-55961","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.","status":"published","published":"2026-06-25T18:16:41.213Z","modified":"2026-06-26T16:50:36.543Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:12:26.045561Z"}],"osv":[{"id":"ALPINE-CVE-2026-55961","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.","status":"published","published":"2026-06-25T18:16:41.213Z","modified":"2026-11-03T06:32:58.087343216Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-03T07:16:09.603409Z"},{"id":"CVE-2026-55961","title":"wolfSSL_PKCS7_verify() reports success for degenerate (certs-only) PKCS#7 with no signer","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.","status":"published","published":"2026-06-25T16:51:18.157Z","modified":"2026-10-28T02:30:42.428801983Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:45:11.609219Z"},{"id":"DEBIAN-CVE-2026-55961","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.","status":"published","published":"2026-06-25T18:16:41.213Z","modified":"2026-10-01T03:03:19.437467287Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:45:57.590991Z"},{"id":"JLSEC-2026-736","title":"`wolfSSL_PKCS7_verify()` returning success for a degenerate (certs-only) PKCS#7 object that contains...","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.","status":"published","published":"2026-07-14T21:41:35.775Z","modified":"2026-07-25T18:24:50.636834028Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"},{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"updated_at":"2026-11-02T15:47:19.003546Z"},{"id":"UBUNTU-CVE-2026-55961","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.","status":"published","published":"2026-06-25T18:16:00Z","modified":"2026-10-17T12:59:09.785804238Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T16:56:41.382716Z"}]}}