CVE-2026-13769: AWS CLI · Incorrect Permissions
Affects AWS CLISource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.34.29 or 1.44.78 when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.34.29, 1.44.78
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade aws/aws-cli to 2.34.29 or 1.44.78.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSAWS CLI | Affected
| Fixed in– |
GitHubaws/aws-clipkg:github/aws/aws-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade AWS CLI to version 1.44.78 (v1) or 2.34.29 (v2) or later to remediate this issue. This is the official fix provided by AWS. Additionally, configuring a restrictive umask on Unix-like systems can help reduce exposure, but upgrading is the recommended and definitive solution.
Description
CVE-2026-13769 is a medium severity vulnerability in AWS CLI versions prior to 1.44.78 (v1) and 2.34.29 (v2) on Unix-like systems. It involves overly permissive file permissions when the system's umask is not configured to restrict file permissions, potentially allowing other local users on the same host to read sensitive credentials generated by certain CLI subcommands. The issue is fixed in AWS CLI versions 1.44.78 and 2.34.29 or later.