Skip to main content

UniFi Protect AI Key CVE-2026-110455

| EUVDEUVD-2026-100816 HIGH
Improper Input Validation (CWE-20)
2026-10-14 Ubiquiti GHSA-3r9g-vjqw-7p76
8.1
CVSS 3.1 · Vendor: Ubiquiti
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain access to device network
  2. Delivery
    Send crafted input to AI Key interface
  3. Exploit
    Bypass improper input validation (CWE-20)
  4. Execution
    Inject OS command
  5. Impact
    Execute arbitrary commands on device

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation targets the UniFi Protect AI Key device and requires the attacker to have access to the network the device is reachable on. The vendor explicitly conditions exploitability on unspecified preconditions ('under certain conditions'), which aligns with the CVSS AC:H rating - the attacker cannot succeed against every deployment and must satisfy environment-specific state that is not attacker-controlled. Per the CVSS vector PR:N/UI:N, no authentication or user interaction is required once network access and those conditions are met. The primary limiting factors are network reachability of the AI Key (not typically exposed to the internet in a default segmented UniFi deployment) and the unspecified AC:H preconditions; the exact configuration or feature state needed is not disclosed in the advisory and should be verified with Ubiquiti.

Impact

The input CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) describes a network-reachable, unauthenticated (PR:N) command injection yielding full confidentiality, integrity, and availability loss - a high-severity profile. However, AC:H is the critical tempering signal: the vendor description's phrase 'under certain conditions' confirms that exploitation is not reliable against arbitrary deployments and depends on conditions outside the attacker's control, which materially lowers real-world exploitability. No EPSS score was provided, the CVE is NOT in CISA KEV, and no public POC is referenced - so there are currently no corroborating signals of active or imminent exploitation. SSVC framing: exploitation status is 'none' observed, automatability is likely low given AC:H, but technical impact is total. Net judgment: a genuine high-impact flaw worth prioritized patching on exposed UniFi Protect AI Key devices, but the AC:H gate plus the absence of EPSS/KEV/POC signals points to it being a lower immediate-threat item than its 8.1 score alone suggests. Missing data to note explicitly: no EPSS probability was supplied, and 'access to the network' in the description is not fully reconciled with PR:N - verify with Ubiquiti whether any adjacency or trust-boundary precondition applies.

Exploit ScenarioDerived

An attacker positioned on the same network as a UniFi Protect AI Key device sends specially crafted input to a vulnerable interface that fails to properly validate it (CWE-20), injecting operating-system commands that execute on the device. Because the CVSS vector is PR:N/UI:N, no authentication or user interaction is required, but AC:H means the attacker must satisfy specific preconditions ('under certain conditions') before the injection succeeds. No public exploit code is referenced, so an attacker would need to develop the exploit independently.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 1.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Command injection in Ubiquiti's UniFi Protect AI Key lets a network-reachable, unauthenticated attacker (CVSS PR:N/UI:N) potentially execute arbitrary operating-system commands on the appliance, giving full loss of confidentiality, integrity, and availability. Per the supplied CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1), exploitation is high-complexity: the vendor conditions success on unspecified preconditions ('under certain conditions'), so attacks are not expected to succeed against every deployment and require the attacker to reach the device's network and satisfy environment-specific state. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was provided; the practical exposure is dominated by whether the AI Key is reachable from untrusted network segments.

RemediationAI

No vendor-released patch or exact fixed firmware version is identified in the available input data; the primary action is to consult Ubiquiti's Security Advisory Bulletin 070 (https://community.ui.com/releases/Security-Advisory-Bulletin-070-070/e7ffc9fa-9129-4a90-b5e3-d597c5ee7a73) and apply the firmware update it specifies as soon as Ubiquiti publishes one, then verify the installed version on the AI Key. Until a fix is confirmed, apply compensating controls that match the high-complexity, network-vector profile: keep the AI Key on an isolated camera/IoT VLAN segmented from user, server, and guest networks by firewall rules that permit only the Protect controller and required management flows (trade-off: overly tight segmentation can break device adoption, analytics updates, or remote management); never port-forward or otherwise expose the device or its management interfaces to the internet; restrict administrative access to a dedicated management network or VPN with authenticated jump hosts; and enable UniFi logging/alerting plus network intrusion detection for anomalous outbound connections from the device, since command injection often manifests as unexpected egress or shell-like traffic (trade-off: alerts require tuning to avoid noise). Because the vendor conditions exploitability on unspecified preconditions, contact Ubiquiti support to clarify which configurations are affected and whether any feature can be disabled to remove the vulnerable code path.

Affected VersionsENISA

UniFi Protect AI Key 0 <2.2.8

Affected Packages

euvd unifi_protect_ai_key fix: 2.2.8

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-20 (Improper Input Validation): the UniFi Protect AI Key does not adequately validate input before it is passed to a command or shell execution path, allowing injection of attacker-controlled commands. The affected asset is identified by the CPE cpe:2.3:a:ubiquiti_inc:unifi_protect_ai_key:*:*:*:*:*:*:*:*, i.e. the Ubiquiti hardware appliance that provides AI-driven analytics within the UniFi Protect camera ecosystem - it is a network-attached edge device, not a general-purpose server, and it typically sits inside a camera/IoT VLAN in a UniFi deployment. The network attack vector (AV:N) with no required privileges or user interaction (PR:N/UI:N) means the injection is triggered over a reachable network service rather than through an authenticated administrative console, but the AC:H rating and Ubiquiti's wording indicate the vulnerable code path is only reachable in particular configurations or states that the attacker must find rather than force. Impact scoring (C:H/I:H/A:H) reflects that successful command injection on the appliance collapses the confidentiality, integrity, and availability of the device and potentially any data or credentials it handles within the Protect ecosystem.

Know when Unifi Protect Ai Key gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Ubiquiti) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Network-reachable and unauthenticated (AV:N/PR:N); AC:H because the vendor's 'under certain conditions' wording signals non-default preconditions; command injection grants full OS control so C:H/I:H/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Ubiquiti).

CVSS VectorVendor: Ubiquiti

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 14, 2026 - 06:01 EUVD
CVE Published
Oct 14, 2026 - 05:00 cve.org
HIGH 8.1

DescriptionCVE.org

A malicious actor with access to the network and under certain conditions could exploit an Improper Input Validation vulnerability found in UniFi Protect AI Key to execute a Command Injection on the device.

Executive ViewAI

Why It Matters

A command-injection flaw in Ubiquiti's UniFi Protect AI Key appliance (CVE-2026-110455, CVSS 8.1) would let an attacker who can reach the device over the network run operating-system commands without authenticating, exposing video and access-control data and potentially enabling full takeover of the appliance. Because no vendor patch is currently available, any AI Key reachable from untrusted or flat network segments represents residual risk to physical-security operations and the sensitive footage and identity data they process. Leadership should care because these devices often sit on camera/access networks that are trusted by default, and a compromise could disrupt surveillance and badge systems while exposing personal data subject to regulatory obligations.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: isolate AI Key appliances on a dedicated VLAN with deny-by-default firewall rules and no internet exposure; restrict management access to trusted administrative hosts; disable unused services and remote-management features; monitor appliance and perimeter logs for anomalous command execution or egress; and maintain a rapid firmware-upgrade plan pending a vendor fix.

Threat Intelligence Overview

EPSS Score
1.2%
Top 32% exploitable
Prevalence
Medium
Ubiquiti UniFi accessory, common in SMB/prosumer surveillance but a specific add-on
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 1.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy