CVE-2026-13769 json
Overly permissive File Permissions in AWS CLI
published 2026-07-01 4 mo ago modified 2026-10-25 14 d ago also GHSA-wfp6-f47h-hxc3 , PYSEC-2026-3548 , EUVD-2026-41116
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
Overly permissive file permissions in AWS CLI before 1.44.78 (v1) and 2.34.29 (v2) on Unix-like systems where the umask has not been configured to restrict file permissions (the default on most systems) may allow other local users on the same host to read credentials written by certain CLI subcommands (aws codeartifact login, aws iam create-virtual-mfa-device, aws deploy register).
To remediate this issue, users should upgrade to AWS CLI 1.44.78 (v1) or 2.34.29 (v2) or later.
Patch / fix
- pypi awscli 1.44.78
- amazon aws_command_line_interface 1.44.78, 2.34.29
- github.com/aws/aws-cli@68811b5 commit
- github.com/aws/aws-cli@84f0ec6 commit
- github.com/aws/aws-cli@e0799fd commit
- github.com/aws/aws-cli#10191 pull request
- github.com/aws/aws-cli#10194 pull request
- github.com/aws/aws-cli#10206 pull request
- github.com/aws/aws-cli/releases/tag/1.44.78 release
- github.com/aws/aws-cli/releases/tag/2.34.29 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-13769 updated cvss 5.5
aws-cli: AWS CLI: Information disclosure via overly permissive file permissions
-
Red Hat Enterprise Linux 9 awscli2 Red Hat Enterprise Linux 10 awscli2affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 4.0 | 6.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | awscli | <1.44.78 |
1.44.78 |
Affected products
- AWS AWS CLI
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/aws/aws-cli/releases/tag/1.44.78
patch, web, release-notes
-
github.com
/aws/aws-cli/releases/tag/2.34.29
patch, web, release-notes
-
github.com
/aws/aws-cli/pull/10191
web
-
github.com
/aws/aws-cli/pull/10194
web
-
github.com
/aws/aws-cli/pull/10206
web
-
github.com
/aws/aws-cli/commit/68811b5ad5cd74d06e944e073ee17bf889babf13
web
-
github.com
/aws/aws-cli/commit/84f0ec6afda03f8a26ff8dea403d02b1b31ee610
web
-
github.com
/aws/aws-cli/commit/e0799fde3c5e3138163e488e42bd3df7a0aa158f
web
-
aws.amazon.com
/security/security-bulletins/2026-049-aws/
vendor-advisory
-
github.com
/aws/aws-cli/security/advisories/GHSA-wfp6-f47h-hxc3
third-party-advisory, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-13769
advisory
-
aws.amazon.com
/security/security-bulletins/2026-049-aws
web
-
github.com
/aws/aws-cli
package
-
pypi.org
/project/awscli
package
-
github.com
/advisories/GHSA-wfp6-f47h-hxc3
advisory
Sources
- CVE List CVE-2026-13769
- GitHub Advisory GHSA-wfp6-f47h-hxc3
- NVD CVE-2026-13769
- OSV PYSEC-2026-3548
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.