Vulnerability in Amazon awscli (CVE-2026-18654)
Summary
Vulnerability in Amazon awscli (CVE-2026-18654). Confidential information can be exposed externally. Mitigation: upgrade to 1.45.28 or later.
Original description
The description as published by the source.
Summary
The AWS Command Line Interface (AWS CLI) is a unified tool to manage AWS services from the command line. An issue exists where the EMR SSH helper commands (aws emr ssh, aws emr socks, aws emr put, aws emr get) passed StrictHostKeyChecking=no to the underlying SSH client, disabling host key verification.
Impact
A network-positioned actor could perform a man-in-the-middle action to intercept SSH sessions and file transfers between the client and EMR cluster instances. Successful exploitation requires the actor to have network access on the path between the client machine and the EMR cluster endpoint. This could result in full visibility of commands executed, files transferred, and credentials passed over the SSH session.
Impacted versions: AWS CLI v1 <= 1.45.27, AWS CLI v2 <= 2.35.2
Patches
This issue has been addressed in AWS CLI v1 version 1.45.28 and AWS CLI v2 version 2.35.3. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
There is no workaround. The insecure SSH option was hardcoded and could not be overridden by the user.
References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHu…
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-18654 has been found in Amazon awscli.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade Amazon awscli to 1.45.28 or later.
If unsure, ask your IT team or search "Amazon awscli CVE-2026-18654" on the vendor's site.
CVE-2026-18654 (Amazon awscli) — CWE-322 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.45.28 — apply immediately
Workaround: There is no workaround.
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-322) exists in Amazon awscli.
Check the vendor advisory for the affected versions of Amazon awscli.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 1.45.28.
Workaround: There is no workaround.
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 temporary workaround mitigate
There is no workaround.パッチが適用されるまでの応急処置として、There is no workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade Amazon awscli to 1.45.28ステージング環境で 1.45.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- AWS aws.amazon.com
- package github.com
- package pypi.org
- web aws.amazon.com
- web github.com
- web github.com
- web github.com
- web aws.amazon.com