GHSA-747p-wmpv-9c78
AWS CLI: cli_history database does not restrict file permissions on Unix systems
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 or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
What each source reports
GitHub Advisories Score used 5.9
AWS CLI: cli_history database does not restrict file permissions on Unix systems
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 or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
- Record
GHSA-747p-wmpv-9c78- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - Weakness
- CWE-276
- Updated
- 2026-11-02
OSV 5.9
AWS CLI: cli_history database does not restrict file permissions on Unix systems
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 or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
- Record
GHSA-747p-wmpv-9c78- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - Weakness
- CWE-276
- Updated
- 2026-11-02
OSVROOT-APP-PYPI-GHSA-747p-wmpv-9c78 5.9
GHSA-747p-wmpv-9c78 in rootio-awscli - Patched by Root
Root has patched GHSA-747p-wmpv-9c78 in the rootio-awscli package for Root:PyPI. Multiple fixed versions available.
- Record
ROOT-APP-PYPI-GHSA-747p-wmpv-9c78- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
awscliPyPI | 1.13.0 up to 1.44.38 | 1.44.38 |
awscliPyPI | 1.13.0 up to 1.44.38, plus listed versions 1.14.01.14.11.14.101.14.111.14.12 Show 45 moreShow less1.14.131.14.141.14.151.14.161.14.171.14.181.14.191.14.21.14.201.14.211.14.221.14.231.14.241.14.251.14.261.14.271.14.281.14.291.14.31.14.301.14.311.14.321.14.331.14.341.14.351.14.361.14.371.14.381.14.391.14.41.14.401.14.411.14.421.14.431.14.441.14.451.14.461.14.471.14.481.14.491.14.51.14.501.14.511.14.521.14.53 | 1.44.38 |
rootio-awscliRoot:PyPI | before 1.43.13+root.io.1 | 1.43.13+root.io.11.43.13+root.io.2 |
awscliRoot:PyPI | before 1.43.13+aikido.2 | 1.43.13+aikido.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-747p-wmpv-9c78 is a medium vulnerability (CVSS 5.9) in awscli, published February 27, 2026. No source lists public exploit code. Fixed in awscli 1.44.38.
References
Left out here: 1,888 versions. The JSON record has them.