{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-6412 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-6412 is a low-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6412 and fix it if it is affected.\n\nWhat it is: CVE-2026-6412 is a low-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6412 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-6412/ (Markdown: https://insights.sbomify.com/CVE-2026-6412/index.md)","id":"CVE-2026-6412","markdown":"https://insights.sbomify.com/CVE-2026-6412/index.md","name":"CVE-2026-6412","record":{"aliases":["DEBIAN-CVE-2026-6412","GHSA-w3gw-f9wr-g6qx","JLSEC-2026-750","UBUNTU-CVE-2026-6412"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SSL/TLS library","requires_auth":"low_privilege","summary":"wolfSSL continues to accept weak SHA-1 and MD5 digests in certificate processing, potentially allowing security bypasses.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssl","vendor":"wolfssl"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Clear","version":"4.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Certificate policy and RFC 8446 compliance concerns regarding the continued acceptance of SHA-1/MD5 in certificate processing.","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":"Continued acceptance of SHA-1/MD5 digests in certificate processing","id":"CVE-2026-6412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wolfssl:wolfssl","products":["wolfssl:wolfssl"],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"@fastify/static vulnerable to route guard bypass via encoded path separators","id":"CVE-2026-6414"},"packages":[],"prev":{"headline":"MAXHUB Pivot Client Application Use of a Broken or Risky Cryptographic Algorithm","id":"CVE-2026-6411"},"products":["wolfSSL"],"published":"2026-06-25","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["wolfSSL"]},"summary":"wolfSSL continues to accept weak SHA-1 and MD5 digests in certificate processing, potentially allowing security bypasses.","url":"https://insights.sbomify.com/CVE-2026-6412/"}