Loading vulnerability…
CVE-2026-34910 is an improper input validation vulnerability in Ubiquiti UniFi OS that permits an attacker with network access to execute arbitrary operating system commands. The package-update service passes an unvalidated package name to a shell; observed exploitation injects commands through the pkg_name parameter with server-side shell execution enabled by by_cmd=true. Chaining the vulnerability with CVE-2026-34908 and CVE-2026-34909 bypasses the authentication gateway and reaches the protected package-update service, enabling unauthenticated root-level remote code execution. Affected products include UniFi OS Server and multiple gateway, console, NVR, NAS, and Express device families. Ubiquiti released fixes in Security Advisory Bulletin 064 on May 21, 2026. Exploitation in the wild has been observed.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains two security artifacts and supporting documentation: a Python exploit script (CVE-2026-34910.py) and a Nuclei template (CVE-2026-34908-unifi-auth-bypass.yaml), plus README and license. Because this repository includes a framework artifact, the main exploit logic is split between a Nuclei detection template for CVE-2026-34908 and a standalone Python PoC for CVE-2026-34910/CVE-2026-34909. The Python script is the primary offensive component. It disables TLS verification, accepts a target URL, and exposes three modes: `--check` to verify the auth bypass by requesting the internal `latest_package` handler through `/api/auth/validate-sso/..%2f..%2f..%2f`, direct command execution by injecting `evil;<command>` into the `pkg_name` query parameter with `by_cmd=true`, and `--read <path>` to retrieve arbitrary files through a traversal path under `/app-assets/users/`. The script treats HTTP 200 responses from the internal handler as success and includes a proof helper that attempts to create `/tmp/PWNED_34910` on the target. The Nuclei YAML is a detection-only template for CVE-2026-34908. It sends a single crafted GET request to `/api/auth/validate-sso/..%2f..%2f..%2fproxy/users/api/v2/ucs/update/latest_package` and matches on HTTP 200 plus response markers such as `pkg_name` and `required`, confirming unauthorized reachability of the internal handler without executing a payload. Overall purpose: demonstrate and operationalize a chain of UniFi OS vulnerabilities affecting pre-SAB-064 systems: CVE-2026-34908 auth bypass, CVE-2026-34909 arbitrary file read, and CVE-2026-34910 unauthenticated command injection RCE. The repository is not just a detector; it contains working exploit code capable of unauthenticated remote command execution and file disclosure against vulnerable UniFi OS Server targets.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
78 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Ubiquiti UniFi OS vulnerability that the actor attempted to chain with two other flaws for root-level remote code execution; CISA identified it as actively exploited.
Vulnerability in Ubiquiti UniFi OS targeted as part of the actor's multi-vector exploitation campaign.
One of three chained vulnerabilities used in attempted remote-code-execution attacks against unpatched Ubiquiti UniFi OS devices.
A critical CVSS 10.0 UniFi OS vulnerability discussed as the third component of a chained compromise affecting UniFi deployments. The content states it is in CISA KEV, has an EPSS score of approximately 0.87, is actively exploited, and has public PoC code, but does not describe its technical root cause.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.