{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-45389 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-45389 is a high-severity authentication bypass vulnerability in n/a, published on 15 Jun 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-45389 and fix it if it is affected.\n\nWhat it is: CVE-2026-45389 is a high-severity authentication bypass vulnerability in n/a, published on 15 Jun 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-45389 in the wild and no public exploit code.\n\nAffected product: n/a. 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-45389/ (Markdown: https://insights.sbomify.com/CVE-2026-45389/index.md)","id":"CVE-2026-45389","markdown":"https://insights.sbomify.com/CVE-2026-45389/index.md","name":"CVE-2026-45389","record":{"aliases":["GHSA-8wf9-g5q8-gg97","OSEC-2026-07"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"OCaml TLS library","requires_auth":"none","summary":"Insufficient certificate checks in OCaml-TLS allow client impersonation when client authentication is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"In OCaml-TLS before 2.1.0, the server implementation does insufficient checks of the certificate provided by the client (when doing client authentication), which allows impersonation with certificates that are not meant for client authentication (because of KeyUsage and ExtendedKeyUsage).","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":"Auth bypass in n/a","id":"CVE-2026-45389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2026-45390"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2026-45388"},"products":["n/a"],"published":"2026-06-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-06-17","vendors":["n/a"]},"summary":"Insufficient certificate checks in OCaml-TLS allow client impersonation when client authentication is enabled.","url":"https://insights.sbomify.com/CVE-2026-45389/"}