How severe is GHSA-9w87-4j72-gcv7?

No CVSS score has been assigned to GHSA-9w87-4j72-gcv7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9w87-4j72-gcv7?

GHSA-9w87-4j72-gcv7 affects the following packages: graphql-code-generator (npm). Ecosystems affected: npm.

How do I fix GHSA-9w87-4j72-gcv7?

Update graphql-code-generator to 0.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9w87-4j72-gcv7 is resolved across your whole dependency graph.

How do I detect GHSA-9w87-4j72-gcv7 in my npm dependencies?

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

How do I mitigate GHSA-9w87-4j72-gcv7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-9w87-4j72-gcv7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9w87-4j72-gcv7 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-9w87-4j72-gcv7 published, and has it been updated?

GHSA-9w87-4j72-gcv7 was published on September 2, 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

Insecure Default Configuration in graphql-code-generatorGHSA-9w87-4j72-gcv7

GHSA-9w87-4j72-gcv7 is a security vulnerability in graphql-code-generator. A fix is available for graphql-code-generator — see the affected versions and patch details below.

Published

Sep 2, 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, a proxy for how much of the ecosystem is exposed.

graphql-code-generatornpm

12Kdownloads / week

Description

Versions of graphql-code-generator prior to 0.18.2 have an Insecure Default Configuration. The packages sets NODE_TLS_REJECT_UNAUTHORIZED to 0, disabling certificate verification for the entire project. This results in Insecure Communication for the process.

Recommendation

Upgrade to version 0.18.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`graphql-code-generator`	all versions	0.18.2`npm install graphql-code-generator@0.18.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql-code-generator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update graphql-code-generator to 0.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9w87-4j72-gcv7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `graphql-code-generator` prior to 0.18.2 have an Insecure Default Configuration. The packages sets `NODE_TLS_REJECT_UNAUTHORIZED` to 0, disabling certificate verification for the entire project. This results in Insecure Communication for the process. ## Recommendation Upgrade to version 0.18.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9w87-4j72-gcv7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works