CVE-2026-13769 AWS CVE debrief

Who should care

System administrators and security teams responsible for Unix-like systems where AWS CLI is used should assess exposure and prioritize remediation. This includes teams managing AWS CLI installations on Unix-like systems, especially where the umask has not been configured to restrict file permissions, and security teams overseeing vulnerability management and remediation efforts.

Why it matters

CVE-2026-13769 is a medium-severity vulnerability in AWS CLI versions before 1.44.78 (v1) and 2.34.29 (v2) on Unix-like systems. The vulnerability is caused by overly permissive file permissions, which may allow other local users on the same host to read credentials written by certain CLI subcommands. System administrators and security teams should assess exposure and prioritize remediation for Unix-like systems where the umask has not been configured to restrict file permissions.

• Local users on the same host may be able to read credentials written by certain CLI subcommands
• Remediation requires upgrading to AWS CLI 1.44.78 (v1) or 2.34.29 (v2) or later
• Configuring umask to restrict file permissions can help prevent exploitation

Technical summary

The vulnerability is caused by 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). This 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).

Defensive priority

Upgrade to AWS CLI 1.44.78 (v1) or 2.34.29 (v2) or later to remediate this issue. System administrators and security teams should assess exposure and prioritize remediation for Unix-like systems where the umask has not been configured to restrict file permissions.

Recommended defensive actions

• Upgrade to AWS CLI 1.44.78 (v1) or 2.34.29 (v2) or later
• Assess exposure and prioritize remediation for Unix-like systems where the umask has not been configured to restrict file permissions
• Configure umask to restrict file permissions
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by overly permissive file permissions in AWS CLI before 1.44.78 (v1) and 2.34.29 (v2) on Unix-like systems. The CVE record and NVD entry provide details on the vulnerability, but do not provide information on exploitation or impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.