{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8989 exists.","fix":"No fix has been published for CVE-2026-8989 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8989 is a high-severity vulnerability in Autel MaxiCharger Single, published on 21 Jul 2026. 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-2026-8989 and fix it if it is affected.\n\nWhat it is: CVE-2026-8989 is a high-severity vulnerability in Autel MaxiCharger Single, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8989 exists.\n\nAffected product: Autel MaxiCharger Single. 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-8989/ (Markdown: https://insights.sbomify.com/CVE-2026-8989/index.md)","id":"CVE-2026-8989","markdown":"https://insights.sbomify.com/CVE-2026-8989/index.md","name":"CVE-2026-8989","record":{"aliases":["GHSA-wpf3-8j9v-2qg2"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging station","requires_auth":"none","summary":"Physical attackers can bypass security restrictions via exposed recovery pins to execute arbitrary code and extract sensitive data from Autel Maxi Charger devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CyberDanube","cpe":[{"product":"maxicharger_single_charger_firmware","vendor":"autel"}],"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-1244","name":"Internal Asset Exposed to Unsafe Debug Access Level or State"},{"id":"CWE-1191","name":"On-Chip Debug and Test Interface With Improper Access Control"}],"description":"Autel Maxi Charger Single firmware through V1.03.51 permits unrestricted access to the NXP i.MX6 recovery mode through exposed hardware recovery pins. An attacker with physical access can boot attacker-controlled code in memory and modify or extract firmware and other sensitive data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Open Recovery Mode","id":"CVE-2026-8989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication Bypass in Kidsview","id":"CVE-2026-8990"},"packages":[],"prev":{"headline":"Access to Bootloader","id":"CVE-2026-8988"},"products":["MaxiCharger Single"],"published":"2026-07-21","related":[{"cvss_score":10,"headline":"Hard-coded / Backdoor Accounts","id":"CVE-2026-8982","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":10,"headline":"Backdoor Authentication Token","id":"CVE-2026-8983","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":10,"headline":"Unauthenticated RCE","id":"CVE-2026-8984","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":10,"headline":"Unauthenticated Command Injection","id":"CVE-2026-8985","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.5,"headline":"Command Injection via Malicious OCPP Server","id":"CVE-2026-8986","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.4,"headline":"Authenticated Heap Overflow","id":"CVE-2026-8987","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.6,"headline":"Access to Bootloader","id":"CVE-2026-8988","kev_date_added":null,"published":"2026-07-21"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["Autel"]},"summary":"Physical attackers can bypass security restrictions via exposed recovery pins to execute arbitrary code and extract sensitive data from Autel Maxi Charger devices.","url":"https://insights.sbomify.com/CVE-2026-8989/"}