How severe is GHSA-747p-wmpv-9c78?

GHSA-747p-wmpv-9c78 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-747p-wmpv-9c78?

GHSA-747p-wmpv-9c78 affects the following packages: awscli (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-747p-wmpv-9c78?

Update awscli to 1.44.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-747p-wmpv-9c78 is resolved across your whole dependency graph.

How do I detect GHSA-747p-wmpv-9c78 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for awscli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-747p-wmpv-9c78 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-747p-wmpv-9c78?

O3 pinpoints whether GHSA-747p-wmpv-9c78 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-747p-wmpv-9c78 actively exploited in the wild?

No public exploit code has been indexed for GHSA-747p-wmpv-9c78 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-747p-wmpv-9c78 published, and has it been updated?

GHSA-747p-wmpv-9c78 was published on February 27, 2026 and was last updated on March 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-747p-wmpv-9c78

MEDIUM

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

Published

Feb 27, 2026

Updated

Mar 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍awscli

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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 or directly via email to [email protected]. Please do not create a public GitHub issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`awscli`	≥ 1.13.0&&< 1.44.38	1.44.38

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for awscli. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update awscli to 1.44.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-747p-wmpv-9c78 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-747p-wmpv-9c78 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-747p-wmpv-9c78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**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 w

O3 Security · Impact-Aware SCA

Is GHSA-747p-wmpv-9c78 in your dependencies?

O3 detects GHSA-747p-wmpv-9c78 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works