Authorization Bypass in graphql-shield
Priority LOW 38CWE-285Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-285.
Summary
Versions of `graphql-shield` prior to 6.0.6 are vulnerable to an Authorization Bypass. The rule caching option `no_cache` relies on keys generated by cryptographically insecure functions, which may cause rules to be incorrectly cached. This allows attackers to access information they should not have access to in case of a key collision. ## Recommendation Upgrade to version 6.0.6 or later.
Why it matters now
Fix Fixed graphql-shield (npm): 6.0.6
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-shield (npm) | before 6.0.6 | 6.0.6 | Patch available | GHSA-hx78-272p-mqqh |
- graphql-shield (npm) Vendor— Affected before 6.0.6 Fixed in 6.0.6 Patch available GHSA-hx78-272p-mqqh
Remediation
- Fix · GHSA-hx78-272p-mqqh graphql-shield (npm) Fixed in 6.0.6 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-hx78-272p-mqqh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences