{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34251 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34251 is a high-severity authentication bypass vulnerability in Tesla Telematics Control Unit (TCU), published on 6 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34251 and fix it if it is affected.\n\nWhat it is: CVE-2025-34251 is a high-severity authentication bypass vulnerability in Tesla Telematics Control Unit (TCU), published on 6 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-34251 in the wild and no public exploit code.\n\nAffected product: Tesla Telematics Control Unit (TCU). 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-34251/ (Markdown: https://insights.sbomify.com/CVE-2025-34251/index.md)","id":"CVE-2025-34251","markdown":"https://insights.sbomify.com/CVE-2025-34251/index.md","name":"CVE-2025-34251","record":{"aliases":["GHSA-jvpj-w5q8-mg28"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tesla TCU firmware","requires_auth":"none","summary":"An attacker with physical access can bypass authentication to execute arbitrary code with root privileges via ADB on Tesla TCU devices.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Tesla Telematics Control Unit (TCU) firmware prior to v2025.14 contains an authentication bypass vulnerability. The TCU runs the Android Debug Bridge (adbd) as root and, despite a “lockdown” check that disables adb shell, still permits adb push/pull and adb forward. Because adbd is privileged and the device’s USB port is exposed externally, an attacker with physical access can write an arbitrary file to a writable location and then overwrite the kernel’s uevent_helper or /proc/sys/kernel/hotplug entries via ADB, causing the script to be executed with root privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Tesla Telematics Control Unit (TCU) \u003c v2025.14 Authentication Bypass","id":"CVE-2025-34251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-34252"},"packages":[],"prev":{"headline":"This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure.","id":"CVE-2025-34250"},"products":["Telematics Control Unit (TCU)"],"published":"2025-10-06","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":"partial"},"state":"PUBLISHED","updated":"2026-05-15","vendors":["Tesla"]},"summary":"An attacker with physical access can bypass authentication to execute arbitrary code with root privileges via ADB on Tesla TCU devices.","url":"https://insights.sbomify.com/CVE-2025-34251/"}