Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.9
AWS CLI: Other users can read command history on Unix systems
GHSA-747p-wmpv-9c78
Summary
If you're using AWS CLI on a multi-user Unix system and have command history enabled, other users on the same system might be able to read your command history. This includes sensitive information like API request and response data. To fix this, update to the latest version of AWS CLI or manually set restrictive permissions on the history file.
What to do
- Update awscli to version 1.44.38.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | awscli | > 1.13.0 , <= 1.44.38 | 1.44.38 |
Original title
AWS CLI: cli_history database does not restrict file permissions on Unix systems
Original description
**Summary**
AWS CLI is a command line tool for interacting with AWS services. When the cli_history feature is enabled, the history database file is created with default permissions, potentially allowing other local users on a multi-user system to read the file.
**Impact**
When cli_history is enabled, AWS CLI stores command history including command parameters and API request/response data in a local SQLite database. On multi-user Unix systems, the default file permissions may allow other local users to read this file, potentially exposing sensitive information. This issue only affects users who have explicitly enabled cli_history, which is disabled by default.
**Impacted versions:** 1.13.0 - 1.44.37 (v1), 2.0.0 - 2.33.20 (v2)
**Patches**
This issue has been addressed in the latest versions 2.33.21 and 1.44.38 of AWS CLI. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
**Workarounds**
Users can manually set restrictive permissions on the history database file. Alternatively, disable cli_history by removing `cli_history = enabled` from the AWS config file.
**Resources**
If there are any questions or comments about this advisory, contact AWS Security via the [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
AWS CLI is a command line tool for interacting with AWS services. When the cli_history feature is enabled, the history database file is created with default permissions, potentially allowing other local users on a multi-user system to read the file.
**Impact**
When cli_history is enabled, AWS CLI stores command history including command parameters and API request/response data in a local SQLite database. On multi-user Unix systems, the default file permissions may allow other local users to read this file, potentially exposing sensitive information. This issue only affects users who have explicitly enabled cli_history, which is disabled by default.
**Impacted versions:** 1.13.0 - 1.44.37 (v1), 2.0.0 - 2.33.20 (v2)
**Patches**
This issue has been addressed in the latest versions 2.33.21 and 1.44.38 of AWS CLI. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
**Workarounds**
Users can manually set restrictive permissions on the history database file. Alternatively, disable cli_history by removing `cli_history = enabled` from the AWS config file.
**Resources**
If there are any questions or comments about this advisory, contact AWS Security via the [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
ghsa CVSS3.1
5.9
Vulnerability type
CWE-276
Incorrect Default Permissions
Published: 27 Feb 2026 · Updated: 7 Mar 2026 · First seen: 6 Mar 2026