# CVE-2026-34910: Ubiquiti UniFi OS Improper Input Validation

> A network-based attacker can execute arbitrary commands on Ubiquiti UniFi OS devices due to improper input validation.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 23 Jun 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-fvgm-jgwh-qwx7

## What is CVE-2026-34910?

CVE-2026-34910 is a critical command injection vulnerability in Ubiquiti Inc EFG, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi OS devices to execute a Command Injection.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 31 products.


Products: Ui Enterprise Fortress Gateway Firmware, Ui Enterprise Network Video Recorder Core Firmware, Ui Enterprise Network Video Recorder Firmware, Ui Unas 2 Firmware, Ui Unas 4 Firmware, Ui Unas Pro 4 Firmware, Ui Unas Pro 8 Firmware, Ui Unas Pro Firmware, Ui Unifi Cloud Gateway Fiber Firmware, Ui Unifi Cloud Gateway Industrial Firmware, Ui Unifi Cloud Gateway Max Firmware, Ui Unifi Cloud Gateway Ultra Firmware, Ui Unifi Cloud Key Plus Firmware, Ui Unifi Cloudkey Enterprise Firmware, Ui Unifi Cloudkey Firmware, Ui Unifi Dream Machine Beast Firmware, Ui Unifi Dream Machine Firmware, Ui Unifi Dream Machine Pro Firmware, Ui Unifi Dream Machine Pro Max Firmware, Ui Unifi Dream Machine Special Edition Firmware and 11 more.

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

No fix has been published for CVE-2026-34910 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Jun 2026.

## Is CVE-2026-34910 being exploited?

Yes. Attackers have exploited CVE-2026-34910 in the wild since at least 23 Jun 2026.

Public exploit code:

- CVE-2026-34910/34909 — UniFi OS unauth RCE + file read via ..%2f auth bypass (CVSS 10.0, KEV, Mirai ITW) (github_poc): https://github.com/Boreas37/CVE-2026-34910-PoC
- CVE-2026-34910 - CVE-2026-34909 Unifi OS (github_poc): https://github.com/gagaltotal/CVE-2026-34910-unifi-poc
- UniFi OS Server - Command Injection (nuclei): http/cves/2026/CVE-2026-34910.yaml

## Other vulnerabilities in Ubiquiti Inc EFG

- [CVE-2026-34908](https://insights.sbomify.com/CVE-2026-34908/): Ubiquiti UniFi OS Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2026-34909](https://insights.sbomify.com/CVE-2026-34909/): Ubiquiti UniFi OS Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2026-34911](https://insights.sbomify.com/CVE-2026-34911/): Path traversal in EFG (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34910 is a critical command injection vulnerability in Ubiquiti Inc EFG, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-34910 in the wild since at least 23 Jun 2026.

Affected product: Ubiquiti Inc EFG. 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-34910/ (Markdown: https://insights.sbomify.com/CVE-2026-34910/index.md)
```

## Sources

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

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