Vulnerability in @genql/cli (CVE-2026-63397)
Summary
Vulnerability in @genql/cli (CVE-2026-63397). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.3.4 or later.
Original description
The description as published by the source.
remorses/genql before version 6.3.4 allows an authenticated attacker with control of the GraphQL schema that is passed to genql to inject arbitrary JavaScript or TypeScript. The malicious code is injected into the generated schema.ts file and executes when the genql client is bundled and imported.
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-63397 has been found in @genql/cli.
Successful exploitation can lead to full system takeover. CVSS score: 6.4/10.
What to do: upgrade @genql/cli to 6.3.4 or later.
If unsure, ask your IT team or search "@genql/cli CVE-2026-63397" on the vendor's site.
CVE-2026-63397 (@genql/cli) — CWE-116 / CVSS v3 6.4
Attack vector: remote (network-reachable)
Patched: 6.3.4 — 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-116) exists in @genql/cli.
Check the vendor advisory for the affected versions of @genql/cli.
Severity: Medium (CVSS 6.4/10). Successful exploitation can lead to full system takeover.
Update to 6.3.4.
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 '@genql/cli' . 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 '@genql/cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@genql/cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @genql/cli to 6.3.4ステージング環境で 6.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory raw.githubusercontent.com
- advisory cve.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com