Vulnerability in Amazon @aws/lsp-codewhisperer (CVE-2026-12957)
Summary
Vulnerability in Amazon @aws/lsp-codewhisperer (CVE-2026-12957). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.0.113 or later.
Original description
The description as published by the source.
Improper trust boundary enforcement in Language Servers for AWS before version 1.65.0 on all supported platforms may allow a for arbitrary code execution. If a local user opens a maliciously crafted workspace, any commands within the project configuration files may be automatically executed. This issue requires the user to trust the workspace when prompted.
To remediate this issue, users should upgrade to Language Servers for AWS version 1.65.0 or higher.
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-12957 has been found in Amazon @aws/lsp-codewhisperer.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Amazon @aws/lsp-codewhisperer to 0.0.113 or later.
If unsure, ask your IT team or search "Amazon @aws/lsp-codewhisperer CVE-2026-12957" on the vendor's site.
CVE-2026-12957 (Amazon @aws/lsp-codewhisperer) — CWE-732 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 0.0.113 — 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 @aws/lsp-codewhisperer.
Check the vendor advisory for the affected versions of Amazon @aws/lsp-codewhisperer.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.113.
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 '@aws/lsp-codewhisperer' . 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 '@aws/lsp-codewhisperer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@aws/lsp-codewhispererを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Amazon @aws/lsp-codewhisperer to 0.0.113ステージング環境で 0.0.113 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- AWS aws.amazon.com
- web github.com
- web github.com
- web github.com
- web github.com
- web aws.amazon.com
- web github.com
- web github.com