dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2026-13769

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AWS CLI versions before 1.44.78 (v1) and 2.34.29 (v2) create credential files with overly permissive permissions (0644) instead of restrictive permissions (0600) when running codeartifact login, iam create-virtual-mfa-device, or deploy register subcommands. On Unix systems with default umask, this allows local users to read sensitive credential data stored in these files.

MitigationUpgrade AWS CLI to version 1.44.78 or higher (v1) or 2.34.29 or higher (v2) to ensure credential files are created with secure permissions (0600).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed AWS CLI version
    Run 'aws --version' to see if you are using v1 or v2 and note the version number
    Affected if Version is before 1.44.78 (v1) or before 2.34.29 (v2)
  2. Identify credential files from codeartifact login
    Look for .pypirc or credential files in user home directory after running 'aws codeartifact login'
    Affected if Files exist and were created by a vulnerable AWS CLI version with permissions 0644 (readable by all users)
  3. Identify credential files from iam create-virtual-mfa-device
    Check for the QR code image file or JSON output file created by 'aws iam create-virtual-mfa-device'
    Affected if Files exist with permissions 0644 instead of 0600 and are readable by other local users
  4. Identify credential files from deploy register
    Check for any temporary credential files created by 'aws deploy register' subcommand
    Affected if Files exist with overly permissive 0644 permissions
  5. Verify file permissions on credential files
    Run 'ls -la <credential_file>' to check octal permissions - look for permissions like 'rw-r--r--' (0644) rather than 'rw-------' (0600)
    Affected if Files show 0644 or more permissive permissions (e.g., 0640, 0645, 0655)

You are affected if your AWS CLI version is below 1.44.78 (v1) or 2.34.29 (v2) AND you have used codeartifact login, iam create-virtual-mfa-device, or deploy register subcommands that created credential files readable by other local users (permissions 0644 or wider).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AWS CLI to version 1.44.78 or higher (v1) or 2.34.29 or higher (v2) to ensure credential files are created with secure permissions (0600).

Recommended fix High confidence

AWS CLI 1.44.78 (v1) or 2.34.29 (v2)

  1. Check the currently installed AWS CLI version by running 'aws --version' to determine if you have v1 or v2 installed
  2. For AWS CLI v1: Upgrade to version 1.44.78 or later using your package manager (e.g., pip install --upgrade awscli==1.44.78 or brew upgrade awscli)
  3. For AWS CLI v2: Upgrade to version 2.34.29 or later using your package manager (e.g., brew upgrade awscli v2 or follow AWS official upgrade instructions)
  4. Verify the upgrade was successful by running 'aws --version' and confirming the version number meets or exceeds the fixed release
  5. Test that the CLI subcommands (codeartifact login, iam create-virtual-mfa-device, deploy register) work as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13769 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data