AWS Kiro IDE 1.0.242 Restricts Agentic Writes from Untrusted Workspaces
Tech GuruQuick Answer
AWS published 2026-117-AWS for Kiro IDE. Upgrade desktop clients to 1.0.242 or later, and investigate global Kiro configuration if an agent operated in an untrusted workspace. AWS publishes no workaround and does not state exploitation status.
Confirm Scope And Apply The Supported Fix
What to do now: Upgrade Kiro IDE to 1.0.242 or later. If an agent ran in an untrusted workspace, review ~/.kiro on macOS/Linux or the .kiro directory under the Windows user profile for unexpected changes, validate settings and file integrity, and retain evidence.
Last verified: 2026-09-27 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Kiro IDE desktop releases before 1.0.242 when agentic features operate in an untrusted workspace |
|---|---|
| Advisory | 2026-117-AWS |
| CVE | CVE-2026-95985 |
| Authoritative release date | 2026-09-24 17:00:00 UTC |
| Authority revision date | No separate revision date published |
| Affected versions | Kiro IDE releases before 1.0.242; applicability requires an agentic workflow in an untrusted workspace that can write outside that workspace. |
| Fixed version | Kiro IDE 1.0.242 or later |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
AWS states that Kiro IDE could permit agentic writes outside an untrusted workspace, including global configuration locations. Version 1.0.242 restricts this behavior; AWS publishes no workaround.
What To Validate Now
- Inventory. Locate Kiro IDE desktop installations, record their versions and owners, and identify sessions where agentic features ran in untrusted workspaces.
- Establish applicability. Compare each installation with AWS's affected range of releases before 1.0.242 and the documented untrusted-workspace condition. Do not infer applicability from product presence alone.
- Remediate. Upgrade to Kiro IDE 1.0.242 or later. AWS publishes no workaround.
- Validate. Confirm the installed version, review global Kiro configuration directories for unauthorized changes, validate expected settings and file integrity, test representative workflows, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Preserve relevant workspace, agent, and filesystem evidence before remediation when compromise is suspected. Test IDE extensions and managed configurations after upgrade; AWS does not state that exploitation has occurred.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
