Insecure Default Configuration in graphql-code-generator
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed graphql-code-generator (npm): 0.18.2
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | graphql-code-generator (npm) | before 0.18.2 | 0.18.2 | Patch available | GHSA-9w87-4j72-gcv7 |
- graphql-code-generator (npm) Vendor— Affected before 0.18.2 Fixed in 0.18.2 Patch available GHSA-9w87-4j72-gcv7
Remediation
- Fix · GHSA-9w87-4j72-gcv7 graphql-code-generator (npm) Fixed in 0.18.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-9w87-4j72-gcv7
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences