{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-6450 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-6450 is a low-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-6450 and fix it if it is affected.\n\nWhat it is: CVE-2026-6450 is a low-severity vulnerability in Wolfssl Wolfssl, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-6450 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-6450/ (Markdown: https://insights.sbomify.com/CVE-2026-6450/index.md)","id":"CVE-2026-6450","markdown":"https://insights.sbomify.com/CVE-2026-6450/index.md","name":"CVE-2026-6450","record":{"aliases":["DEBIAN-CVE-2026-6450","GHSA-qpch-gjf6-c9gf","JLSEC-2026-751","UBUNTU-CVE-2026-6450"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"wolfSSL TLS library","requires_auth":"high_privilege","summary":"Attackers can bypass CRL critical extension checks in wolfSSL if CRL support is enabled and signatures are trusted, allowing revoked certificates to be accepted.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssl","vendor":"wolfssl"}],"cvss":{"score":1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"A CRL critical extension bypass exists in ParseCRL_Extensions where critical extensions are not properly enforced, allowing a crafted CRL with an unhandled critical extension to be accepted. This only affects builds with CRL support enabled and where a crafted CRL had a trusted signature when parsed.","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":"CRL critical extension bypass in ParseCRL_Extensions","id":"CVE-2026-6450","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wolfssl:wolfssl","products":["wolfssl:wolfssl"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"CMS für Motorrad Werkstätten \u003c= 1.0.0 - Cross-Site Request Forgery","id":"CVE-2026-6451"},"packages":[],"prev":{"headline":"Auth bypass in Booking for Appointments and Events Calendar – Amelia","id":"CVE-2026-6449"},"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":"Attackers can bypass CRL critical extension checks in wolfSSL if CRL support is enabled and signatures are trusted, allowing revoked certificates to be accepted.","url":"https://insights.sbomify.com/CVE-2026-6450/"}