{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7414 exists.","fix":"No fix has been published for CVE-2026-7414 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7414 is a critical vulnerability in Yarbo Firmware, published on 7 May 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-7414 and fix it if it is affected.\n\nWhat it is: CVE-2026-7414 is a critical vulnerability in Yarbo Firmware, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7414 exists.\n\nAffected product: Yarbo Firmware. 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-7414/ (Markdown: https://insights.sbomify.com/CVE-2026-7414/index.md)","id":"CVE-2026-7414","markdown":"https://insights.sbomify.com/CVE-2026-7414/index.md","name":"CVE-2026-7414","record":{"aliases":["GHSA-vw42-99fw-3p5g"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Yarbo robot firmware","requires_auth":"none","summary":"Hardcoded administrative credentials in Yarbo robot firmware allow unauthorized access to device management interfaces, requiring a firmware upgrade to remediate.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AHA","cpe":[{"product":"lawn_mower_firmware","vendor":"yarbo"},{"product":"lawn_mower_pro_firmware","vendor":"yarbo"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Yarbo firmware v2.3.9 contains hardcoded administrative credentials embedded in the firmware image. These credentials are identical across all devices running this firmware and cannot be changed or removed by end users, enabling trivial unauthorized access to device management interfaces by anyone who knows them.","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":"Hardcoded credentials in Yarbo robot firmware","id":"CVE-2026-7414","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Open MQTT orchestration without read/write ACLs in Yarbo robot firmware","id":"CVE-2026-7415"},"packages":[],"prev":{"headline":"Persistent undocumented backdoor access in Yarbo robot","id":"CVE-2026-7413"},"products":["Firmware"],"published":"2026-05-07","related":[{"cvss_score":9.8,"headline":"Open MQTT orchestration without read/write ACLs in Yarbo robot firmware","id":"CVE-2026-7415","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":7.2,"headline":"Persistent undocumented backdoor access in Yarbo robot","id":"CVE-2026-7413","kev_date_added":null,"published":"2026-05-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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-07","vendors":["Yarbo"]},"summary":"Hardcoded administrative credentials in Yarbo robot firmware allow unauthorized access to device management interfaces, requiring a firmware upgrade to remediate.","url":"https://insights.sbomify.com/CVE-2026-7414/"}