Vulnerability in @aws/lsp-codewhisperer (CVE-2026-12958)
Summary
Vulnerability in @aws/lsp-codewhisperer (CVE-2026-12958). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.0.117 or later.
Original description
The description as published by the source.
Missing symlink validation in Language Servers for AWS may allow an arbitrary file write outside of the workspace trust boundary. This may occur when a local user opens a workspace with a maliciously crafted symlink that resolves to a file path outside the workspace trust boundary.
To remediate this issue, users should upgrade to version 1.69.0 or higher.
Source: NIST National Vulnerability Database 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-12958 has been found in @aws/lsp-codewhisperer.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade @aws/lsp-codewhisperer to 0.0.117 or later.
If unsure, ask your IT team or search "@aws/lsp-codewhisperer CVE-2026-12958" on the vendor's site.
CVE-2026-12958 (@aws/lsp-codewhisperer) — CWE-61 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 0.0.117 — 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-61) exists in @aws/lsp-codewhisperer.
Check the vendor advisory for the affected versions of @aws/lsp-codewhisperer.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.117.
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 @aws/lsp-codewhisperer to 0.0.117ステージング環境で 0.0.117 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com
- web aws.amazon.com
- web github.com
- web github.com
- web github.com