# AWS CLI: cli_history database does not restrict file permissions on Unix systems

Advisory record · `GHSA-747p-wmpv-9c78`

- **Identifiers:** `GHSA-747p-wmpv-9c78`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-276](https://cwe.mitre.org/data/definitions/276.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 27 Feb 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Feb 2026, 15:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `awscli` (PyPI): affected `>=1.13.0, <1.44.38`; fixed in `1.44.38`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The awscli PyPI package versions 1.13.0 up to 1.44.38 (fixed in 1.44.38) creates its cli_history database with default file permissions when the feature is enabled, which can let other local users on multi-user Unix systems read stored command history, parameters, and API request and response data. An attacker needs a local account on the same system and cli_history must be turned on, which is off by default. Upgrade to awscli 1.44.38 or 2.33.21, or disable cli_history by removing it from the AWS config file, or restrict the history database file's permissions manually.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:37 UTC: First seen by agentprime
- 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-747p-wmpv-9c78)

## Sources

- [GitHub Advisory Database: GHSA-747p-wmpv-9c78](https://github.com/advisories/GHSA-747p-wmpv-9c78)
- [OSV: GHSA-747p-wmpv-9c78](https://osv.dev/vulnerability/GHSA-747p-wmpv-9c78)
- <https://github.com/aws/aws-cli/security/advisories/GHSA-747p-wmpv-9c78>
- <https://github.com/aws/aws-cli>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-747p-wmpv-9c78>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-747p-wmpv-9c78/>. Everything for agents: <https://agentprime.io/llms.txt>.
