AWS patches Kiro CLI session transcript credential exposure flaw

What happened.Amazon Web Services resolved a high-severity local privilege escalation flaw in the AWS Kiro interface that left chat histories and cloud tokens readable by local accounts.
Why it matters.Command-line artificial intelligence agents often execute system tasks with elevated developer credentials. When CLI utilities write session transcripts with world-readable permissions, shared workstation boundaries fail. Security teams must ensure developer laptops update to version 1.4.2 immediately.
The technical specifications:
- Permission flaw: Tracked as CVE-2026-124848 in bulletin 2026-178-AWS with a 7.8 CVSS score, the defect stems from overly permissive file creation modes in the workspace log manager.
- Credential exposure: Kiro recorded model interaction transcripts, command outputs, and temporary STS credentials using standard world-readable file masks on shared workstations.
- Local exploitation: Non-root users or background processes running on developer laptops could read stored chat sessions to exfiltrate active cloud tokens without elevated privileges.
- Affected versions: The flaw impacts AWS Kiro CLI versions prior to 1.4.2 across Linux and macOS.
- Remediation release: AWS issued Kiro CLI version 1.4.2, applying restrictive 0600 file permissions to configuration directories and session logs.
STORYLINE PROGRESSION & CONTEXT
This report represents a verified evolution of prior newsroom intelligence: