Loading vulnerability…
CVE-2026-10591 is an insufficient access control vulnerability in the file write tool of Amazon Kiro IDE before version 0.11. The flaw allows remote unauthenticated actors to supply crafted instructions that cause the IDE to write attacker-controlled content to execution-sensitive paths, including workspace task configuration files that can be processed automatically by the development environment. By abusing the IDE's ability to modify files such as Visual Studio Code task configuration within a project, an attacker can plant commands that are subsequently auto-executed when the affected folder is opened. The issue effectively turns an unsafe file-write primitive into arbitrary command execution in the context of the user running Kiro IDE.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Kiro vulnerability in which code written to .vscode/tasks.json could be auto-executed when a folder was opened.
A separate Kiro vulnerability involving an agent file-write flaw that enabled auto-execution of a poisoned .vscode/tasks.json on folder open; patched in Kiro 0.11.
A vulnerability in Amazon Kiro IDE before version 0.11 involving insufficient access control in the file write tool that could allow remote unauthenticated attackers to achieve arbitrary command execution by writing to execution-sensitive paths.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.