Which versions of type-graphql are affected by GHSA-XF64-2F9P-6PQQ?

type-graphql (npm) versions < 0.17.6 is affected.

Is there a fix for GHSA-XF64-2F9P-6PQQ?

Yes. GHSA-XF64-2F9P-6PQQ is fixed in 0.17.6. Upgrade to this version or later.

Is GHSA-XF64-2F9P-6PQQ exploitable, and should I be worried?

Whether GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ?

Upgrade type-graphql to 0.17.6 or later.

GHSA-XF64-2F9P-6PQQ in type-graphql

Q: What is GHSA-XF64-2F9P-6PQQ?

GHSA-XF64-2F9P-6PQQ is a low-severity security vulnerability in type-graphql (npm), affecting versions < 0.17.6. It is fixed in 0.17.6.

Q: Is there a fix for GHSA-XF64-2F9P-6PQQ?

Yes. GHSA-XF64-2F9P-6PQQ is fixed in 0.17.6. Upgrade to this version or later.

Q: Is GHSA-XF64-2F9P-6PQQ exploitable, and should I be worried?

Whether GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ?

Upgrade type-graphql to 0.17.6 or later.

GHSA-XF64-2F9P-6PQQ

GHSA-XF64-2F9P-6PQQ is a low-severity security vulnerability in type-graphql (npm), affecting versions < 0.17.6. It is fixed in 0.17.6.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Information Exposure in type-graphql

Versions of type-graphql prior to 0.17.6 are vulnerable to Information Exposure. The package leaks the resolver source code in an error message. It is possible to force this error when no subscription topics are provided in the request.

Impact

Affected versions

type-graphql (< 0.17.6)

Security releases

type-graphql → 0.17.6 (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 to version 0.17.6 or later.

Frequently Asked Questions

What is GHSA-XF64-2F9P-6PQQ? GHSA-XF64-2F9P-6PQQ is a low-severity security vulnerability in type-graphql (npm), affecting versions < 0.17.6. It is fixed in 0.17.6.
Which versions of type-graphql are affected by GHSA-XF64-2F9P-6PQQ? type-graphql (npm) versions < 0.17.6 is affected.
Is there a fix for GHSA-XF64-2F9P-6PQQ? Yes. GHSA-XF64-2F9P-6PQQ is fixed in 0.17.6. Upgrade to this version or later.
Is GHSA-XF64-2F9P-6PQQ exploitable, and should I be worried? Whether GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ 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 GHSA-XF64-2F9P-6PQQ? Upgrade type-graphql to 0.17.6 or later.