CVSS 4.0
6.8 mediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NMedium (6.8) in amazon aws command line interface. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in awscli 1.44.78.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Nawscli (PyPI): fixed in 1.44.78Explain CVE-2026-13769 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13769?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13769?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13769 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| AWS CLI | through 1.44.77 |
| AWS CLI | through 2.34.28 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wfp6-f47h-hxc3 | PyPI | awscli | <1.44.78 | 1.44.78 |
| PYSEC-2026-3548 | PyPI | awscli | <1.44.78 | 1.44.78 |
Red Hat rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | awscli2 | Fix deferred | |
| Red Hat Enterprise Linux 9 | awscli2 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13769.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-732 (11).