{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25834 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-25834 is a medium-severity vulnerability in n/a, published on 1 Apr 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-25834 and fix it if it is affected.\n\nWhat it is: CVE-2026-25834 is a medium-severity vulnerability in n/a, published on 1 Apr 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-25834 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-25834/ (Markdown: https://insights.sbomify.com/CVE-2026-25834/index.md)","id":"CVE-2026-25834","markdown":"https://insights.sbomify.com/CVE-2026-25834/index.md","name":"CVE-2026-25834","record":{"aliases":["ALPINE-CVE-2026-25834","DEBIAN-CVE-2026-25834","GHSA-8j6f-944f-8jmj","UBUNTU-CVE-2026-25834"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mbed TLS library","requires_auth":"none","summary":"Attackers can force a downgrade to weaker cryptographic algorithms in Mbed TLS, compromising communication security.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mbed_tls","vendor":"trustedfirmware"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Mbed TLS v3.3.0 up to 3.6.5 and 4.0.0 allows Algorithm Downgrade.","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":"Security feature bypass in n/a","id":"CVE-2026-25834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2026-25835"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-25833"},"products":["n/a"],"published":"2026-04-01","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2026-34875","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-49195","kev_date_added":null,"published":"2024-10-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45158","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2024-45159","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":9.8,"headline":"Mbed TLS 3.2.x through 3.4.x before 3.5 has a Buffer Overflow that can lead to remote Code execution.","id":"CVE-2023-45199","kev_date_added":null,"published":"2023-10-07"},{"cvss_score":9.1,"headline":"An issue was discovered in Mbed TLS 3.5.0 through 4.0.0.","id":"CVE-2026-34873","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.1,"headline":"In Mbed TLS 3.3.0 through 3.5.2 before 3.6.0, a malicious client can cause information disclosure or a denial of service because of a stack","id":"CVE-2024-30166","kev_date_added":null,"published":"2024-04-03"}],"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-04-01","vendors":["n/a"]},"summary":"Attackers can force a downgrade to weaker cryptographic algorithms in Mbed TLS, compromising communication security.","url":"https://insights.sbomify.com/CVE-2026-25834/"}