Skip to main content
Mallory
Critical

Command Injection in Ubiquiti UniFi OS package-update service

IdentifiersCVE-2026-34910CWE-20· Improper Input Validation

CVE-2026-34910 is an improper input validation vulnerability in Ubiquiti UniFi OS, specifically in the package-update service used by UniFi OS Server and referenced more broadly across UniFi OS devices. Available reporting indicates the vulnerable backend interpolated attacker-controlled package-name input into a shell command of the form sudo /usr/bin/uos runnable latest-versions %v and executed it via a sh -c wrapper without sufficient sanitization. This creates a command-injection condition that allows arbitrary shell metacharacters or crafted input to alter the intended command flow. Bishop Fox reporting further states the flaw was reachable in an unauthenticated exploit chain on UniFi OS Server 5.0.6 and earlier when combined with CVE-2026-34908 and CVE-2026-34909 to bypass authentication and reach the vulnerable package-update endpoint. The initial command execution occurs as the ucs-update service account rather than directly as root.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary command execution on the affected device. In the documented UniFi OS Server exploit chain, attackers can reach the vulnerable endpoint without credentials by chaining CVE-2026-34908 and CVE-2026-34909, then use CVE-2026-34910 to execute commands as the ucs-update account. Reporting indicates that account has passwordless sudo access to several binaries, making escalation to root trivial on tested systems. Root compromise can expose highly sensitive material stored on the UniFi OS management plane, including JWT signing keys, TLS private keys, cloud-access tokens, PostgreSQL user data, RADIUS secrets, Wi-Fi credentials, VPN/WireGuard configurations, NFC card data, facial-recognition templates, and OS password hashes. A successful attacker may obtain persistent administrative control over the UniFi environment and potentially compromise managed network devices, surveillance systems, door-access systems, and associated identities.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict network exposure of UniFi OS management interfaces, especially from untrusted networks and the public Internet. Limit access to the package-update and related management endpoints through segmentation, VPN-only administration, ACLs, and reverse-proxy filtering where feasible. Monitor for requests involving /api/auth/validate-sso/ combined with encoded traversal sequences and for access to ucs/update/latest_package, as well as suspicious child processes spawned by ucs-update and unexpected sudo activity. Use available safe detection tooling from Bishop Fox to identify vulnerable UniFi OS Server instances. If exploitation is suspected, perform incident response actions beyond patching, including credential and secret rotation, review for forged administrative sessions, and host-level forensic investigation.

Remediation

Patch, then assume compromise.

Upgrade to vendor-fixed releases. For UniFi OS Server, available reporting states the issue is fixed in version 5.0.8 and later, and Bishop Fox confirmed the unauthenticated exploit chain does not work on 5.0.8. Ubiquiti’s fixes reportedly included package-name validation, removal of shell-based execution in favor of safer argument-array execution in the backend, and partial sudoers hardening for the ucs-update account. Where applicable, follow Ubiquiti’s product-specific fixed-version guidance for other affected UniFi OS devices. Because patching does not remediate prior compromise, organizations should also investigate for signs of exploitation, rotate exposed secrets, and invalidate trust material such as signing keys if compromise is suspected.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
UbiquitiUnifi Osapplication
UbiquitiUnifi Os Serveroperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity14

Community discussion across Reddit, Mastodon, and other social sources.