{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5393 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-5393 is a medium-severity memory corruption vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5393 and fix it if it is affected.\n\nWhat it is: CVE-2026-5393 is a medium-severity memory corruption vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5393 in the wild and no public exploit code.\n\nAffected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5393/ (Markdown: https://insights.sbomify.com/CVE-2026-5393/index.md)","id":"CVE-2026-5393","markdown":"https://insights.sbomify.com/CVE-2026-5393/index.md","name":"CVE-2026-5393","record":{"aliases":["DEBIAN-CVE-2026-5393","GHSA-f4w6-5m9p-28hw","JLSEC-2026-721","UBUNTU-CVE-2026-5393"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"wolfSSL TLS library","requires_auth":"none","summary":"An out-of-bounds read in wolfSSL's dual-algorithm CertificateVerify processing can cause crashes or leak memory when experimental features are enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssl","vendor":"wolfssl"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Dual-Algorithm CertificateVerify out-of-bounds read. When processing a dual-algorithm CertificateVerify message, an out-of-bounds read can occur on crafted input. This can only occur when --enable-experimental and --enable-dual-alg-certs is used when building wolfSSL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OOB Read in DoTls13CertificateVerify with WOLFSSL_DUAL_ALG_CERTS","id":"CVE-2026-5393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wolfssl:wolfssl","products":["wolfssl:wolfssl"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pimcore Platform v12.3.3 - SQL Injection in DataObject composite index handling","id":"CVE-2026-5394"},"packages":[],"prev":{"headline":"wolfSSL heap OOB read in PKCS7 SignedData streaming","id":"CVE-2026-5392"},"products":["wolfSSL"],"published":"2026-04-09","related":[{"cvss_score":10,"headline":"Buffer overread in domain name matching","id":"CVE-2024-5991","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-37155","kev_date_added":null,"published":"2021-07-21"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-36177","kev_date_added":null,"published":"2021-01-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2896","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2897","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2014-2898","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-16748","kev_date_added":null,"published":"2019-09-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-10","vendors":["wolfSSL"]},"summary":"An out-of-bounds read in wolfSSL's dual-algorithm CertificateVerify processing can cause crashes or leak memory when experimental features are enabled.","url":"https://insights.sbomify.com/CVE-2026-5393/"}