Kiro CLI 2.27.0 Restricts Local Transcript and Prompt-History Access
Tech GuruQuick Answer
Upgrade to Kiro CLI 2.27.0 and launch it once. Check owner-only access to existing transcripts and secure the legacy Amazon Q history file where applicable; assess whether stored credentials require response.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify macOS and Linux hosts, all local users, Kiro CLI versions, previous Amazon Q CLI use and retained history locations. Check versions 1.16.0 through before 2.27.0 and shared-host access. The issue concerns local file confidentiality, not a claim that every recorded secret was accessed. Upgrade and launch the CLI once. For earlier Amazon Q 1.16.0–1.19.x use, delete or restrict ~/.aws/amazonq/.cli_bash_history as AWS directs. If upgrade must wait, use the authority’s owner-only permissions and umask guidance. Inspect ownership and access permissions without printing history or secrets. Verify that a subsequent session creates owner-only files and confirm the legacy file is handled.
Last verified: 2026-11-11 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Kiro CLI, formerly Amazon Q Developer CLI, on macOS and Linux |
|---|---|
| Advisory | 2026-178-AWS |
| CVE | CVE-2026-124848 |
| Authoritative release date | November 10, 2026 at 12:45 PST (20:45 UTC), from the primary AWS bulletin. |
| Authority revision date | No separate revision date is stated. The RSS summary says 12:00 PST; the primary bulletin’s 12:45 PST release time controls this notice. |
| Affected versions | Kiro CLI 1.16.0 through versions before 2.27.0 on macOS and Linux. Other local users on the same host could read session transcripts and prompt history, including sensitive content present in those files. |
| Fixed version | Kiro CLI 2.27.0 or later, launched once to restrict existing session files |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | AWS does not state malicious exploitation in this bulletin.; no exploitation claim is inferred. |
What Changed
AWS corrected permissive local session-file permissions. The bulletin also requires handling the separate legacy Amazon Q CLI history file for users of versions 1.16.0 through 1.19.x.
What To Validate Now
- Inventory. Identify macOS and Linux hosts, all local users, Kiro CLI versions, previous Amazon Q CLI use and retained history locations.
- Establish applicability. Check versions 1.16.0 through before 2.27.0 and shared-host access. The issue concerns local file confidentiality, not a claim that every recorded secret was accessed.
- Remediate. Upgrade and launch the CLI once. For earlier Amazon Q 1.16.0–1.19.x use, delete or restrict ~/.aws/amazonq/.cli_bash_history as AWS directs. If upgrade must wait, use the authority’s owner-only permissions and umask guidance.
- Validate. Inspect ownership and access permissions without printing history or secrets. Verify that a subsequent session creates owner-only files and confirm the legacy file is handled.
- 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
Do not paste transcript contents into tickets. Retain access and version evidence, and handle any credentials found in exposed history under the organization’s incident-response process.
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.
