What is CVE-2026-63397?

CVE-2026-63397 is a high-severity security vulnerability in @genql/cli (npm), affecting versions < 6.3.4. It is fixed in 6.3.4.

How severe is CVE-2026-63397?

CVE-2026-63397 has a CVSS score of 6.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @genql/cli are affected by CVE-2026-63397?

@genql/cli (npm) versions < 6.3.4 is affected.

Is there a fix for CVE-2026-63397?

Yes. CVE-2026-63397 is fixed in 6.3.4. Upgrade to this version or later.

Is CVE-2026-63397 exploitable, and should I be worried?

Whether CVE-2026-63397 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-63397 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-63397 in @genql/cli

Q: How severe is CVE-2026-63397?

CVE-2026-63397 has a CVSS score of 6.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @genql/cli are affected by CVE-2026-63397?

@genql/cli (npm) versions < 6.3.4 is affected.

Q: Is there a fix for CVE-2026-63397?

Yes. CVE-2026-63397 is fixed in 6.3.4. Upgrade to this version or later.

Q: Is CVE-2026-63397 exploitable, and should I be worried?

Whether CVE-2026-63397 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-63397 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-63397?

Upgrade @genql/cli to 6.3.4 or later.

Summary

Genql: inject arbitrary JavaScript or TypeScript via a GraphQL schema

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.

Impact

CVE-2026-63397 has a CVSS score of 6.4 (High). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.3.4); upgrading removes the vulnerable code path.

Affected versions

@genql/cli (< 6.3.4)

Security releases

@genql/cli → 6.3.4 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade @genql/cli to 6.3.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-63397? CVE-2026-63397 is a high-severity security vulnerability in @genql/cli (npm), affecting versions < 6.3.4. It is fixed in 6.3.4.
How severe is CVE-2026-63397? CVE-2026-63397 has a CVSS score of 6.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @genql/cli are affected by CVE-2026-63397? @genql/cli (npm) versions < 6.3.4 is affected.
Is there a fix for CVE-2026-63397? Yes. CVE-2026-63397 is fixed in 6.3.4. Upgrade to this version or later.
Is CVE-2026-63397 exploitable, and should I be worried? Whether CVE-2026-63397 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-63397 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-63397? Upgrade @genql/cli to 6.3.4 or later.