{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-89134 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-89134 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-89134 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 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-89134 and fix it if it is affected.\n\nWhat it is: CVE-2026-89134 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 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-89134 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-89134/ (Markdown: https://insights.sbomify.com/CVE-2026-89134/index.md)","id":"CVE-2026-89134","markdown":"https://insights.sbomify.com/CVE-2026-89134/index.md","name":"CVE-2026-89134","record":{"aliases":["DEBIAN-CVE-2026-89134","GHSA-p2xv-vrwq-543q","UBUNTU-CVE-2026-89134"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"wolfSSL TLS library","requires_auth":"none","summary":"Attackers can bypass TLS name constraints by using non-DNS SANs, allowing acceptance of out-of-scope certificates in wolfSSL.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-\u003esubjectCN != NULL \u0026\u0026 cert-\u003ealtNames == NULL \u0026\u0026 !cert-\u003eisCA instead of \"no dNSName SAN\", so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Subject CN name-constraint check bypassed when non-DNS SAN present","id":"CVE-2026-89134","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":1,"next":{"headline":"Failed X509_verify_cert leaves unverified CA in shared CertManager","id":"CVE-2026-89135"},"packages":[],"prev":{"headline":"NameConstraints not enforced across unconstrained intermediate CA","id":"CVE-2026-89133"},"products":["wolfSSL"],"published":"2026-09-27","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-09-29","vendors":["wolfSSL"]},"summary":"Attackers can bypass TLS name constraints by using non-DNS SANs, allowing acceptance of out-of-scope certificates in wolfSSL.","url":"https://insights.sbomify.com/CVE-2026-89134/"}