Quick answers
- Is CVE-2026-13769 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13769 being exploited in the wild.
- How severe is CVE-2026-13769?
- High severity, with a CVSS score of 5.5, published 1 July 2026.
- Which products and versions are affected?
- Amazon Web Services AWS CLI <= 1.44.77; awscli (PyPI) <= 1.44.77, ECOSYSTEM:introduced=0,fixed=1.44.78.
- Is there a fix for CVE-2026-13769?
- Yes. awscli (PyPI): upgrade to 1.44.78 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13769 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-13769?
- Check whether you run Amazon AWS, Amazon Web Services AWS CLI or awscli (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- awscli (PyPI): upgrade to 1.44.78 or later
pip install "awscli>=1.44.78"
Technical details
The vulnerability is a file permissions misconfiguration in AWS CLI where credential and configuration files are created with overly permissive permissions (likely world-readable or group-readable). An attacker with local file system access can directly read these files to extract AWS access keys and configuration details. The attack vector is local; no network access is required, but the attacker must have access to the same system where AWS CLI is configured. This enables credential theft and subsequent unauthorized API access to AWS services under the compromised identity. Patch availability should be confirmed via AWS security bulletins.
Affected products
- AWS AWS CLI
Identifiers
- CVE-2026-13769
- GHSA-wfp6-f47h-hxc3
- PYSEC-2026-3548
Timeline
- 2026-09-22: disclosed