AWS Kiro IDE 1.0.242 Restricts Agentic Writes from Untrusted Workspaces
Tech GuruQuick Answer
Upgrade Kiro IDE to 1.0.242 or later if it is affected by 2026-117-AWS. Agentic work in an untrusted workspace could write outside that workspace, including global Kiro configuration. Updating the IDE does not establish that earlier configuration changes were legitimate.
Confirm Scope And Apply The Supported Fix
Next step: Record affected desktop versions and untrusted-workspace sessions. Review ~/.kiro on macOS/Linux or the user's Windows .kiro directory against an approved baseline, preserving suspicious evidence before repair.
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
Workspace trust should constrain what an agent can modify. This flaw crosses that boundary into locations reused by other sessions. AWS provides no workaround in the bulletin, so keep the software update and the review of existing global settings as separate tasks.
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 and expected global settings, extensions, and integrations. Use a disposable authorized workspace to test the intended restrictions. Keep any agent logs or file comparisons sanitized, since they can include project paths or credentials.
- 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.
