{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14942 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14942 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14942 is a critical authentication bypass vulnerability in wolfSSL wolfSSH, published on 6 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-14942 and fix it if it is affected.\n\nWhat it is: CVE-2025-14942 is a critical authentication bypass vulnerability in wolfSSL wolfSSH, published on 6 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-14942 in the wild and no public exploit code.\n\nAffected product: wolfSSL wolfSSH. 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-2025-14942/ (Markdown: https://insights.sbomify.com/CVE-2025-14942/index.md)","id":"CVE-2025-14942","markdown":"https://insights.sbomify.com/CVE-2025-14942/index.md","name":"CVE-2025-14942","record":{"aliases":["GHSA-5r65-89wp-6mxr"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"wolfSSH library","requires_auth":"none","summary":"Attackers can bypass authentication or leak passwords in wolfSSH client applications by manipulating the key exchange state machine.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssh","vendor":"wolfssh"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/U:Red","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"wolfSSH’s key exchange state machine can be manipulated to leak the client’s password in the clear, trick the client to send a bogus signature, or trick the client into skipping user authentication. This affects client applications with wolfSSH version 1.4.21 and earlier. Users of wolfSSH must update or apply the fix patch and it’s recommended to update credentials used. This fix is also recommended for wolfSSH server applications. While there aren’t any specific attacks on server applications, the same defect is present. Thanks to Aina Toky Rasoamanana of Valeo and Olivier Levillain of Telecom SudParis for the report.","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":"Authentication Bypass","id":"CVE-2025-14942","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2025-14943"},"packages":[],"prev":{"headline":"GZSEO \u003c= 2.0.11 - Authenticated (Contributor+) Authorization Bypass to Stored Cross-Site Scripting","id":"CVE-2025-14941"},"products":["wolfSSH"],"published":"2026-01-06","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2022-32073","kev_date_added":null,"published":"2022-07-13"},{"cvss_score":9.4,"headline":"Host verification bypass and credential leak","id":"CVE-2025-11625","kev_date_added":null,"published":"2025-10-21"},{"cvss_score":9.1,"headline":"User authentication bypass in wolfSSH server","id":"CVE-2024-2873","kev_date_added":null,"published":"2024-03-25"},{"cvss_score":9,"headline":"wolfSSH ECDSA host key curve not validated against negotiated algorithm","id":"CVE-2026-16516","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.7,"headline":"wolfSSHd on Windows race condition leading to logon token reused across connections","id":"CVE-2026-83540","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":6.9,"headline":"Denial of service in wolfSSH","id":"CVE-2026-84897","kev_date_added":null,"published":"2026-10-07"}],"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":"total"},"state":"PUBLISHED","updated":"2026-01-06","vendors":["wolfSSL"]},"summary":"Attackers can bypass authentication or leak passwords in wolfSSH client applications by manipulating the key exchange state machine.","url":"https://insights.sbomify.com/CVE-2025-14942/"}