# CVE-2026-7413: Persistent undocumented backdoor access in Yarbo robot

> Attackers can exploit a hidden backdoor in Yarbo robot firmware to gain unauthenticated privileged access, bypassing security controls.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-pq5m-hxx2-xhw5

## What is CVE-2026-7413?

CVE-2026-7413 is a high-severity authentication bypass vulnerability in Yarbo Firmware, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A hidden, persistent backdoor was found in Yarbo firmware v2.3.9 that provides remote, unauthenticated (or weakly authenticated) access to privileged functionality. The backdoor is undocumented, cannot be disabled via user-facing settings, and survives factory reset and ordinary firmware updates.

Weakness: CWE-912 (Hidden Functionality)

## Which versions are affected by CVE-2026-7413?

It affects 2 products.


Products: Yarbo Lawn Mower Firmware, Yarbo Lawn Mower Pro Firmware.

## How do I fix CVE-2026-7413?

No fix has been published for CVE-2026-7413 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7413 exists.

## Other vulnerabilities in Yarbo Firmware

- [CVE-2026-7414](https://insights.sbomify.com/CVE-2026-7414/): Hardcoded credentials in Yarbo robot firmware (critical 9.8)
- [CVE-2026-7415](https://insights.sbomify.com/CVE-2026-7415/): Open MQTT orchestration without read/write ACLs in Yarbo robot firmware (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7413 and fix it if it is affected.

What it is: CVE-2026-7413 is a high-severity authentication bypass vulnerability in Yarbo Firmware, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7413 exists.

Affected product: Yarbo Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7413/ (Markdown: https://insights.sbomify.com/CVE-2026-7413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7413
- OSV: https://osv.dev/vulnerability/CVE-2026-7413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7413/
Summaries are generated and may contain mistakes; the official description above is the record.