Vulnerability in Amazon awscli (CVE-2026-13769)
Summary
Vulnerability in Amazon awscli (CVE-2026-13769). Confidential information can be exposed externally. Mitigation: upgrade to 1.44.78 or later.
Original description
The description as published by the source.
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.
Source: AWS Security Bulletins NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-13769 has been found in Amazon awscli.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade Amazon awscli to 1.44.78 or later.
If unsure, ask your IT team or search "Amazon awscli CVE-2026-13769" on the vendor's site.
CVE-2026-13769 (Amazon awscli) — CWE-732 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: 1.44.78 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-732) exists in Amazon awscli.
Check the vendor advisory for the affected versions of Amazon awscli.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 1.44.78.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'awscli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'awscli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
awscliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Amazon awscli to 1.44.78ステージング環境で 1.44.78 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory aws.amazon.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- AWS aws.amazon.com
- package github.com
- package pypi.org
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web aws.amazon.com