{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-22094 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22094 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22094 is a critical vulnerability in EVbee DC 80, published on 29 Sep 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-22094 and fix it if it is affected.\n\nWhat it is: CVE-2026-22094 is a critical vulnerability in EVbee DC 80, published on 29 Sep 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-22094 in the wild and no public exploit code.\n\nAffected product: EVbee DC 80. 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-22094/ (Markdown: https://insights.sbomify.com/CVE-2026-22094/index.md)","id":"CVE-2026-22094","markdown":"https://insights.sbomify.com/CVE-2026-22094/index.md","name":"CVE-2026-22094","record":{"aliases":["GHSA-m8j5-qffh-wq39"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"EVbee DC 80","requires_auth":"none","summary":"Attackers can gain root access via SSH due to a weak hardcoded password in the EVbee DC 80 firmware.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DIVD","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1391","name":"Use of Weak Credentials"}],"description":"The firmware for the EVbee DC-80 has a weak hardcoded root password, which allows attackers to login as root using the SSH daemon that is exposed to the network.","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":"Weak root password in EVbee DC 80","id":"CVE-2026-22094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in diagnosis web endpoint","id":"CVE-2026-22095"},"packages":[],"prev":{"headline":"Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app","id":"CVE-2026-22093"},"products":["DC 80"],"published":"2026-09-29","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["EVbee"]},"summary":"Attackers can gain root access via SSH due to a weak hardcoded password in the EVbee DC 80 firmware.","url":"https://insights.sbomify.com/CVE-2026-22094/"}