Skip to main content
VulnerabilityPublished Updated

CVE-2026-13769: AWS CLI · Overly permissive File Permissions

Affects aws-shellSource GCVE Database

0
Compare
Authoritative record:CVE-2026-13769· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.2.2_14 when convenient.

Data as of 1 Nov 2026, 02:08 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.2.2_14
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 31 Oct 2026.

What to do

Upgrade aws-shell to 0.2.2_14.

Affected software

ProductAffectedFixed in
Homebrewaws-shellpkg:brew/aws-shellOther threatsAffected
  • >=0.1.0 <0.2.2_14
Fixed in
  • 0.2.2_14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade AWS CLI to version 1.44.78 or later for v1, or 2.34.29 or later for v2 to apply the official fix that corrects file permissions. Ensure any forked or derivative codebases incorporate these fixes. No additional mitigation is required once patched.

Description

Certain AWS CLI subcommands on Unix-like systems with default umask settings wrote credential and configuration files with overly permissive world-readable permissions (0644) instead of owner-only (0600). This could allow other local users on the same host to read sensitive credentials. The affected AWS CLI versions are v1 up to 1.44.77 and v2 up to 2.34.28. The issue has been fixed in AWS CLI v1 version 1.44.78 and v2 version 2.34.29.

References

Community reviews

Loading reviews…