CVE-2026-105788

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

GHSA-6ppj-5886-4f26 ↗EUVD-2026-93405 ↗

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.
microsoft UFO
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-780, permanent identifier
pkg:pypi/microsoft/UFO
14d 21h 41msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h53m
0
+4h
+6h
+8h
+10h
+12h

description

UFO versions before 3.0.10 allow authenticated Mobile MCP input to alter commands sent to a connected Android device through ADB. An attacker with a valid Mobile MCP API key and access to an ADB-authorized reachable device could run additional commands as that device's Android shell user.

mitigation

Upgrade UFO to version 3.0.10 or later. Restrict Mobile MCP API keys and limit ADB authorization and network reachability to trusted devices and users.

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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
1.1%63rd percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 14:05Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-780",
  "cve_id": "CVE-2026-105788",
  "display_id": "CVE-2026-105788",
  "ghsa_id": "GHSA-6ppj-5886-4f26",
  "euvd_id": "EUVD-2026-93405",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated Android shell command injection in UFO",
  "summary": "UFO versions before 3.0.10 allow authenticated Mobile MCP input to alter commands sent to a connected Android device through ADB. An attacker with a valid Mobile MCP API key and access to an ADB-authorized reachable device could run additional commands as that device's Android shell user.",
  "mitigation": "Upgrade UFO to version 3.0.10 or later. Restrict Mobile MCP API keys and limit ADB authorization and network reachability to trusted devices and users.",
  "vendor": "microsoft",
  "product": "UFO",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= be75a7d"
      ],
      "ecosystem": "pip",
      "fixed_versions": [],
      "package_name": "microsoft/UFO",
      "purl": "pkg:pypi/microsoft/UFO"
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0106,
  "epss_percentile": 0.6391,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.526174533333334,
  "t0_at": "2026-10-06T14:05:24.022000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T14:05:24.022000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T14:05:24.022000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105788"
    }
  }
}

published 2026-10-06 15:44Z
last change 2026-10-21 12:26Z

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.