Incorrect Default File Permissions
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.27.0 when convenient.
Data as of 10 Nov 2026, 22:34 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 5.5 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 6.8 |
- Patch
- Available – fixed in 2.27.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Kiro CLI to 2.27.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AmazonKiro CLI | Affected
| Fixed in
|
Description
Incorrect default file permissions in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and Linux might allow other local users on the same host to read a user's session transcripts and prompt history, including any credentials or source code they contain. The CLI created its local session storage files with permissions that made them readable by all local users. To remediate this issue, users should upgrade to Kiro CLI version 2.27.0 or later and launch it once. 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.