CVE-2026-110455

waiting for further signalsZero needs more public information before it can validate it.

GHSA-3r9g-vjqw-7p76 ↗EUVD-2026-100816 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Ubiquiti Inc UniFi Protect AI Key < 2.2.8
fixed in 2.2.8
CWE-20 Improper Input Validation
ETK-2026-1569Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 14h 21msince last run
2h 03mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+75h14m
0
+2h
+4h
+6h
+8h
+10h

description

UniFi Protect AI Key versions 2.2.6 and earlier are affected by an input-validation flaw that can lead to command injection. An attacker with network access may be able to run commands on the device when additional, unspecified conditions are met.

mitigation

Upgrade UniFi Protect AI Key to version 2.2.8 or later. Restrict network access to the device to trusted administrative networks until upgrades are complete.

fixed in 2.2.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
1.2%67th percentile
agent run time
2h 03m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 05:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 05:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-110455

{
  "etk_id": "ETK-2026-1569",
  "cve_id": "CVE-2026-110455",
  "display_id": "CVE-2026-110455",
  "ghsa_id": "GHSA-3r9g-vjqw-7p76",
  "euvd_id": "EUVD-2026-100816",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Command injection in UniFi Protect AI Key",
  "summary": "UniFi Protect AI Key versions 2.2.6 and earlier are affected by an input-validation flaw that can lead to command injection. An attacker with network access may be able to run commands on the device when additional, unspecified conditions are met.",
  "mitigation": "Upgrade UniFi Protect AI Key to version 2.2.8 or later. Restrict network access to the device to trusted administrative networks until upgrades are complete.",
  "vendor": "Ubiquiti Inc",
  "product": "UniFi Protect AI Key",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.2.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.2.8"
      ],
      "package_name": "UniFi Protect AI Key",
      "purl": null
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0121,
  "epss_percentile": 0.6787,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 122.58254786666667,
  "t0_at": "2026-10-14T05:00:58.120000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T05:00:58.120000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T05:00:58.120000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110455"
    }
  }
}

published 2026-10-14 12:57Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.