aws-shell · AWS CLI: cli_history database does not restrict file permissions on Unix systems
Affects aws-shellSource GCVE Database
CVSS 5.9 Medium : upgrade to 0.2.2_11 when convenient.
Data as of 1 Nov 2026, 02:08 UTC
- Patch
- Available – fixed in 0.2.2_11
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LWhat to do
Upgrade aws-shell to 0.2.2_11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewaws-shellpkg:brew/aws-shellOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade AWS CLI to version 1.44.38 or later for v1, or 2.33.21 or later for v2, where the issue is fixed. Alternatively, users can disable cli_history by removing 'cli_history = enabled' from the AWS config file or manually set restrictive file permissions on the history database file to prevent unauthorized access.
Description
AWS CLI versions 1.13.0 through 1.44.37 (v1) and 2.0.0 through 2.33.20 (v2) have a vulnerability in the cli_history feature where the history database file is created with default Unix file permissions. This can allow other local users on multi-user Unix systems to read sensitive command history data. The issue affects only users who have explicitly enabled cli_history, which is disabled by default. The vulnerability is fixed in AWS CLI versions 1.44.38 and 2.33.21.