Skip to content
VulniPulse
Medium5.5Red Hat Linux

Medium [CVE-2026-13769] Information disclosure via overly permissive file permissions

This medium-severity Red Hat Linux advisory covers CVE-2026-13769 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat package: awscli2.

CVE-2026-13769 Published Jul 1, 2026Updated by vendor Jul 1, 2026
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. This vulnerability can lead to information disclosure, potentially exposing sensitive user credentials to unauthorized local attackers.

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.

Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; Red Hat package: awscli2.

Affected versions
  • < 1.44.78
  • < 2.34.29

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • 1.44.78
  • 2.34.29

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / 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.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.