CVE-2026-13769
Description
A flaw was found in AWS CLI. Overly permissive file permissions on Unix-like systems, where the umask has not been configured to restrict file permissions, may allow other local users on the same host to read credentials. This occurs when certain AWS CLI subcommands, such as aws codeartifact login, aws iam create-virtual-mfa-device, or aws deploy register, write credentials. This vulnerability can lead to information disclosure, potentially exposing sensitive user credentials to unauthorized local attackers.
Statement
Successful exploitation requires an attacker to already have local access to the same Unix-like host as the targeted user. Additionally, the vulnerability relies on the system having an unrestricted umask configuration and requires the victim to manually execute specific AWS CLI subcommands (such as codeartifact login or iam create-virtual-mfa-device) that write credentials to the filesystem.
Impact Limitations: The direct impact is strictly limited to localized information disclosure. While the exposure of sensitive AWS credentials is a serious risk that could lead to the compromise of external AWS resources, the vulnerability itself does not allow an attacker to escalate privileges, achieve remote code execution, or compromise the integrity and availability of the local host system.
Mitigation
To mitigate this issue, configure a more restrictive umask for users who execute AWS CLI subcommands that handle credentials. Setting a umask of `0077` or `0027` will prevent other local users from reading newly created files. This can be achieved by adding `umask 0077` (or `umask 0027`) to the user's shell profile (e.g., `~/.bashrc` or `~/.profile`). Users must log out and back in for the new umask to take effect. This mitigation applies to newly created files and does not affect existing files with overly permissive permissions.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 5.5 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality,Integrity
Technical Impact: Read Application Data; Modify Application Data
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
