BCY-ADV-2026-014
CRITICAL — CVSS 10.0 (3 CVEs)
Ubiquiti UniFi OS — Unauthenticated RCE Chain
CVE-2026-34908 / 34909 / 34910 · Auth Bypass → File Traversal → Command Injection → Root
CVE-2026-34908
CVE-2026-34909
CVE-2026-34910
CVSS 10.0
CISA KEV
Unauthenticated RCE
Root Privilege
UniFi OS
Network Infrastructure
Actively Exploited
Prepared by Warren Barr · Barr Cyber LLC · barr-cyber.com · July 2026
What This Is
Three CVSS 10.0 vulnerabilities in Ubiquiti UniFi OS — each critical on its own — chain together to give any network-reachable attacker unauthenticated root access on UniFi OS devices. No credentials required. No user interaction required. The chain affects every UniFi OS-powered device: Cloud Gateways, network appliances, Dream Machines, Protect NVRs, Access hubs, and Talk appliances. CISA added all three to the Known Exploited Vulnerabilities catalog on June 23, 2026 with a three-day remediation deadline. Censys identified approximately 100,000 internet-facing UniFi OS endpoints globally, with roughly 50,000 in the United States.
Three CVEs. One HTTP request. Full root on your network gateway, cameras, or physical access controllers. If your UniFi console is internet-facing and unpatched, your entire network infrastructure is owned.
CVE Details
CVE-2026-34908 — CVSS 10.0 — CWE-284 (Improper Access Control)
The authentication gateway NGINX processes crafted requests with a divergence between the raw URI and the normalized URI. A request beginning with an auth-exempt prefix passes the authentication check in raw form, but after normalization routes to an authenticated internal endpoint. This is the bypass that opens the door.
CVE-2026-34909 — CVSS 10.0 — CWE-22 (Path Traversal)
A path traversal in the internal file management handler permits reading and writing arbitrary files on the underlying UniFi OS host, including sensitive configuration files, signing keys, and credential stores. Used together with the auth bypass, this is exploitable without authentication.
CVE-2026-34910 — CVSS 10.0 — CWE-20 (Improper Input Validation)
The package-update service passes a user-supplied package name directly to a shell command without validation. Combined with the auth bypass, this enables arbitrary OS command injection against the service account running package updates — which holds passwordless sudo privileges over dpkg, chmod, and systemctl, making privilege escalation to root trivial via a malicious .deb package.
CISA KEV: All three added June 23, 2026. Deadline June 26, 2026 (BOD 26-04)
Patch: UniFi OS Server 5.0.8 (released May 21, 2026)
Affected: UniFi OS Server 5.0.6 and earlier (all hardware running UniFi OS)
How the Chain Works
BishopFox researchers documented and published the full exploit chain. The attack proceeds as follows:
Step 1 — Auth bypass (34908 + 34909): The attacker sends a request with a URI that passes the authentication exemption check in raw form. NGINX normalizes the path before routing, and the normalized form reaches an authenticated internal API endpoint. The authentication check has already passed and is not re-evaluated on the normalized path. The attacker is now inside the authenticated surface.
Step 2 — Command injection (34910): The attacker accesses the package-update service endpoint through the bypass. This endpoint accepts a package name and passes it to a shell command. No validation is performed on the package name. The attacker injects a command. The service account executing the update holds passwordless sudo privileges over dpkg, chmod, and systemctl.
Step 3 — Root escalation: Using the sudo access, the attacker installs a crafted .deb package or executes privileged commands directly. Full root on the UniFi OS host. From root, the attacker can read the UniFi secret store (signing keys, TLS certificates, cloud tokens, login database, network configuration), create persistent backdoors, and pivot through connected network infrastructure.
Active exploitation has been observed creating rogue administrator accounts named "John Sim" during automated reconnaissance sweeps — a reliable indicator of compromise when found in UniFi controller logs.
Scale of Exposure
UniFi is the dominant networking platform for small and mid-sized organizations — it controls gateways, switches, wireless APs, cameras, physical access panels, and VoIP across hundreds of thousands of deployments. Many of these consoles are internet-accessible because administrators use Ubiquiti's remote management features or expose the management port directly. Censys tracked approximately 100,000 internet-facing instances globally. At patch release on May 21, 2026, zero-day exploitation had not been publicly confirmed. By June 23 when CISA added all three to KEV, active exploitation was confirmed in the wild.
Detection
Check your UniFi OS version via SSH:
ubnt@unifi:~$ ubnt-device-info summary | grep "UniFi OS"
# Look for version 5.0.8 or later.
# Any version 5.0.6 or earlier is vulnerable.
# Alternative: check in the UniFi web interface
# Settings → System → Controller Configuration → Version
Hunt for the rogue "John Sim" administrator account:
# In UniFi OS → Admins & Users
# Look for accounts you did not create — specifically "John Sim"
# Any unrecognized admin account is an indicator of compromise
# Via SSH on the UniFi console:
cat /data/unifi-core/db/system.db | grep -i "john\|rogue\|unknown"
Check for unauthorized file modifications (BishopFox safe detection tool):
# BishopFox published a safe, read-only detection tool on GitHub.
# It probes the vulnerable endpoint without executing any command.
# If reachable, confirms whether CVE-2026-34908 auth bypass is open.
# github.com/BishopFox/CVE-2026-34908-check
python3 cve_2026_34908_check.py <unifi-ip>
# VULNERABLE = bypass is open (unpatched)
# PATCHED = NGINX returns 400 (5.0.8+ behavior)
Review recent administrator account creation in UniFi logs:
grep -i "account\|admin\|technician\|created" /var/log/unifi/*.log | \
grep "$(date -d '30 days ago' +%Y-%m-%d)"
IOCs
CVEs CVE-2026-34908, CVE-2026-34909, CVE-2026-34910
Rogue account "John Sim" administrator (automated recon sweep signature)
Signing key Compromise of /data/unifi-core/config/jwt.yaml (rotate after breach)
Secrets at risk UniFi secret store: signing keys, TLS certs, cloud tokens, DB creds
Persistence .deb package install via dpkg sudo, systemctl service modification
Recon pattern HTTP requests with raw-vs-normalized URI divergence to port 8443/11443
CISA KEV All three CVEs added June 23, 2026. Deadline June 26, 2026.
Remediation
A patched restore does NOT automatically rotate the potentially exfiltrated signing key. Restoring a configuration backup after reinstalling UniFi OS will restore the old (possibly compromised) JWT signing key unless you explicitly replace it. Manual rotation is required.
Sources & References
BCY-ADV-2026-014 · Published July 2026 · Barr Cyber LLC · Kalispell, MT
More like this, when it happens
Advisories only. No newsletter, no marketing, unsubscribe in one click.
Barr Cyber — Network Hardening & Endpoint Security
Ubiquiti UniFi is standard equipment in homes, small businesses, and mid-sized organizations across Montana and the Flathead Valley. If your UniFi console is internet-accessible or has never been audited, contact Barr Cyber for a network hardening assessment.
Get in Touch →