---
id: "CVE-2026-124848"
page: "https://infrastack.ai/live/CVE-2026-124848"
kind: "vulnerability"
aliases: ["CVE-2026-124848"]
title: "Incorrect default file permissions in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and\u2026"
severity: "medium"
cvss: 6.8
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "amazon-q-developer-cli", "aws", "kiro-cli", "lab-disclosure", "linux", "macos", "shared-hosts"]
not_affected_if: ["kiro-cli-2.27.0-or-later", "single-user-machine", "windows"]
published_at: "2026-11-10T20:19:07+00:00"
first_seen_at: "2026-11-10T20:36:01+00:00"
updated_at: "2026-11-10T20:46:04+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/2026-178-aws/", "first_seen_at": "2026-11-10T20:36:01+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-124848", "first_seen_at": "2026-11-10T20:46:04+00:00"}]
exploit_sources: []
---

# Incorrect default file permissions in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and…

Link for people: https://infrastack.ai/live/CVE-2026-124848 (this .md is for agents)

Kiro CLI, an AI coding assistant for the terminal, wrote session transcripts and prompt history with permissions that let other local users on the same host read them. A local user can read prompts, model responses, tool output, and any credentials or source code in them.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Kiro CLI version with `kiro-cli --version` (exact command unknown; the sources do not confirm the binary name); affected if below `2.27.0`.
- Look at permissions on `~/.kiro` and, for Amazon Q Developer CLI 1.16.0 through 1.19.x, on `~/.aws/amazonq/.cli_bash_history`; other local users should not be able to read them.

## Fix

- Kiro CLI: upgrade to `2.27.0` or later.
- Users who ran Amazon Q Developer CLI `1.16.0` through `1.19.x`: the sources also say to delete `~/.aws/amazonq/.cli_bash_history` or restrict it to the owner.

## Timeline

- 2026-11-10T20:36:01+00:00 lab https://aws.amazon.com/security/security-bulletins/2026-178-aws/ — AWS: CVE-2026-124848 - Incorrect default permissions on session transcripts and prompt history in Kiro CLI
- 2026-11-10T20:46:04+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-124848

## Documents

- [advisory] AWS: CVE-2026-124848 - Incorrect default permissions on session transcripts and prompt history in Kiro CLI https://aws.amazon.com/security/security-bulletins/2026-178-aws/
- [mentions] AWS Security Bulletins: CVE-2026-124848 - Incorrect default permissions on session transcripts and prompt history in Kiro CLI https://aws.amazon.com/security/security-bulletins/rss/2026-178-aws/

## From the sources

CVE-2026-124848 - Incorrect default permissions on session transcripts and prompt history in Kiro CLI

### CVE-2026-124848 - Incorrect default permissions on session transcripts and prompt history in Kiro CLI

Bulletin ID: 2026-178-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/10/2026 12:45 PM PST

 Description:

Kiro CLI is an AI coding assistant that runs in the terminal.

We identified CVE-2026-124848, an issue in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and Linux. Kiro CLI created its session transcript and prompt history files with permissions that allowed other local users on the same host to read them. Another local user might read a user's prompts, model responses and tool output, including any credentials or source code they contain.

Impacted versions: Kiro CLI >= 1.16.0 AND < 2.27.0

Resolution:

This issue has been addressed in Kiro CLI version 2.27.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Users should launch the upgraded Kiro CLI once so existing session files are restricted to the owner. Users who ran Amazon Q Developer CLI 1.16.0 through 1.19.x should also delete the ~/.aws/amazonq/.cli_bash_history file or restrict it to the owner.

Workarounds:

Users who cannot upgrade immediately can restrict access to the owner by running "chmod -R go-rwx ~/.kiro" on macOS and Linux, and by running "umask 077" in the shell before launching Kiro CLI so that new files are created owner-only. Users who ran Amazon Q Developer CLI 1.16.0 through 1.19.x should also run "chmod go-rwx ~/.aws/amazonq/.cli_bash_history".

References:

- CVE-2026-124848

 Please email aws-security@amazon.com with any s ecurity questions or concerns.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_