How severe is GHSA-xf64-2f9p-6pqq?

No CVSS score has been assigned to GHSA-xf64-2f9p-6pqq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xf64-2f9p-6pqq?

GHSA-xf64-2f9p-6pqq affects the following packages: type-graphql (npm). Ecosystems affected: npm.

How do I fix GHSA-xf64-2f9p-6pqq?

Update type-graphql to 0.17.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xf64-2f9p-6pqq is resolved across your whole dependency graph.

How do I detect GHSA-xf64-2f9p-6pqq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for type-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xf64-2f9p-6pqq if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-xf64-2f9p-6pqq actively exploited in the wild?

No public exploit code has been indexed for GHSA-xf64-2f9p-6pqq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xf64-2f9p-6pqq published, and has it been updated?

GHSA-xf64-2f9p-6pqq was published on September 4, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Information Exposure in type-graphqlGHSA-xf64-2f9p-6pqq

GHSA-xf64-2f9p-6pqq is a security vulnerability in type-graphql. A fix is available for type-graphql — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

512other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

type-graphqlnpm

911Kdownloads / week

Description

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.

Recommendation

Upgrade to version 0.17.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`type-graphql`	all versions	0.17.6`npm install type-graphql@0.17.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for type-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update type-graphql to 0.17.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xf64-2f9p-6pqq is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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. ## Recommendation Upgrade to version 0.17.6 or later.

O3 Security · Impact-Aware SCA

Is GHSA-xf64-2f9p-6pqq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works