JLSEC-2026-736

See a problem?
Please try reporting it to the source first.

Source

https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-736.md

Import Source

https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-736.json

JSON Data

https://api.osv.dev/v1/vulns/JLSEC-2026-736

Upstream

CVE-2026-55961

EUVD-2026-39491

GHSA-cj56-5c53-9qjf

Published

2026-07-14T21:41:35.775Z

Modified

2026-07-25T18:24:50.636834028Z

Severity

7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
8.2 (High) CVSS_V4 - 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 CVSS Calculator

Summary

`wolfSSL_PKCS7_verify()` returning success for a degenerate (certs-only) PKCS#7 object that contains...

Details

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.

Database specific

{
    "sources": [
        {
            "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2026-55961",
            "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-55961",
            "modified": "2026-06-26T16:50:36.543Z",
            "id": "CVE-2026-55961",
            "published": "2026-06-25T18:16:41.213Z",
            "imported": "2026-07-17T22:33:23.057Z",
            "database_specific": {
                "status": "Analyzed"
            }
        },
        {
            "html_url": "https://github.com/advisories/GHSA-cj56-5c53-9qjf",
            "modified": "2026-06-26T18:33:49Z",
            "id": "GHSA-cj56-5c53-9qjf",
            "published": "2026-06-25T18:30:41Z",
            "imported": "2026-07-17T22:33:23.238Z",
            "url": "https://api.github.com/advisories/GHSA-cj56-5c53-9qjf"
        },
        {
            "html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-39491",
            "modified": "2026-06-25T17:57:46Z",
            "id": "EUVD-2026-39491",
            "published": "2026-06-25T16:51:18Z",
            "imported": "2026-07-17T22:33:33.026Z",
            "url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-39491"
        }
    ],
    "license": "CC-BY-4.0"
}

References

Affected packages

Julia / wolfSSL_jll

Package

Name: wolfSSL_jll
Purl: pkg:julia/wolfSSL_jll?uuid=98c43586-9870-5ae5-ab22-acc77b9bbdb5

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

5.9.2+0

Database specific

source

"https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-736.json"