{
 "public_id": "AIR-2026-0253",
 "incident_id": "2026-06-cymulate-ai-cli-binary-resolution-rce",
 "date_disclosed": "2026-06-04",
 "date_occurred": null,
 "title": "Cymulate: untrusted-binary resolution and config-file poisoning give code execution in Cursor CLI, AWS Kiro, Codex, Gemini CLI and GitHub Copilot CLI",
 "class": "responsible_disclosure",
 "attack_surface": "coding_agent",
 "initial_vector": "prompt_injection_file_write_then_untrusted_executable_resolution",
 "agent_capability_abused": [
  "file_write_tool",
  "tool_discovery_search_path",
  "workspace_config_autoload"
 ],
 "target_product": "Cursor CLI; AWS Kiro; OpenAI Codex; Gemini CLI; GitHub Copilot CLI",
 "target_vendor": "Cursor; Amazon Web Services; OpenAI; Google; GitHub (Microsoft)",
 "autonomy_level": "semi_autonomous",
 "impact_realized": false,
 "impact_type": [
  "remote_code_execution"
 ],
 "blast_radius": "Windows users of the listed CLIs and Kiro IDE users who open a poisoned repository or process injected content",
 "cve": [
  "CVE-2026-10591"
 ],
 "taxonomy": {
  "owasp_asi": [
   "ASI01",
   "ASI05"
  ],
  "mitre_atlas": [],
  "labels": [
   "binary_planting",
   "untrusted_search_path",
   "config_poisoning",
   "coordinated_disclosure"
  ]
 },
 "defense_present": "vendor approval and sandbox models, which the research reports as not engaged by the attack chain",
 "defense_bypassed": true,
 "fix_shipped": "Kiro fixed in 0.11 (AWS bulletin 2026-037-AWS); other vendors vary, see notes",
 "primary_sources": [
  "https://cymulate.com/blog/zero-click-rce-prompt-injection-ai-tools/",
  "https://aws.amazon.com/security/security-bulletins/2026-037-aws/"
 ],
 "verified_quote": "Simply opening a project or interacting with AI-generated content can trigger the attack chain",
 "confidence": "high",
 "notes": "One record for the coordinated disclosure. CVE-2026-10591 and AWS bulletin 2026-037-AWS cover only the Kiro file-write issue (writes to execution-sensitive paths such as the workspace task configuration; fixed in Kiro 0.11 with explicit approval now required). Per-vendor outcomes as stated by Cymulate: Cursor CLI report closed as informative and still vulnerable at publication; GitHub Copilot CLI triaged, bounty paid, severity downgraded to low, no fix committed; Gemini CLI acknowledged, remediation status unknown; Codex desktop report closed without meaningful technical engagement. Cymulate separately published a deeper Codex write-up. Cymulate describes the vendor responses collectively as ranging from thorough engagement to dismissal. Quote is from Cymulate; the AWS bulletin carries the Kiro CVE text. Demonstrated only; no exploitation reported.",
 "risk_category": "security_fraud",
 "risk_secondary": [],
 "risk_subcategory": "Prompt Injection",
 "risk_sub_secondary": [
  "Remote Code Execution & Sandbox Escape"
 ],
 "ai_entity": "generative",
 "agency": "agent_acted",
 "agency_debatable": true,
 "agency_reason": "the planting step uses the agent's own file-write tool, after which the CLI resolves the attacker-placed binary; contested because the final execution is conventional binary resolution",
 "vector_family": "indirect_prompt_injection",
 "vector_detail": "prompt_injection_file_write_then_untrusted_executable_resolution",
 "guardrail_kind": [
  "human_approval",
  "sandbox_isolation"
 ],
 "guardrail_outcome": "silent",
 "xrefs": {
  "aiid": [],
  "atlas": [],
  "cve": [
   "CVE-2026-10591"
  ],
  "ghsa": []
 },
 "primary_asi": "ASI01",
 "agent_framework": "unknown",
 "model_provider": "multiple",
 "model_name": "",
 "detection_mechanism": "unknown",
 "tool_access": "unknown",
 "financial_loss_band": "unknown",
 "eai_category": "privilege_escalation",
 "eai_domain": "access_control_and_permissions",
 "eai_secondary": [],
 "eai_reason": "impact rule: privilege_escalation",
 "asi_curated": [],
 "asi_scope": "in_scope",
 "asi_provenance": "rule",
 "asi_reason": "ASI01 (vector_family=indirect_prompt_injection); ASI05 (impact=code_exec)",
 "submitted_by": "EAI Internal"
}