How severe is GHSA-hx78-272p-mqqh?

No CVSS score has been assigned to GHSA-hx78-272p-mqqh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hx78-272p-mqqh?

GHSA-hx78-272p-mqqh affects the following packages: graphql-shield (npm). Ecosystems affected: npm.

How do I fix GHSA-hx78-272p-mqqh?

Update graphql-shield to 6.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx78-272p-mqqh is resolved across your whole dependency graph.

How do I detect GHSA-hx78-272p-mqqh in my npm dependencies?

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

How do I mitigate GHSA-hx78-272p-mqqh 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-hx78-272p-mqqh actively exploited in the wild?

No public exploit code has been indexed for GHSA-hx78-272p-mqqh 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-hx78-272p-mqqh published, and has it been updated?

GHSA-hx78-272p-mqqh was published on September 3, 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

Authorization Bypass in graphql-shieldGHSA-hx78-272p-mqqh

GHSA-hx78-272p-mqqh is a security vulnerability in graphql-shield. A fix is available for graphql-shield — see the affected versions and patch details below.

Published

Sep 3, 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.

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

graphql-shieldnpm

311Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`graphql-shield`	all versions	6.0.6`npm install graphql-shield@6.0.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql-shield, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update graphql-shield to 6.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx78-272p-mqqh 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-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.

O3 Security · Impact-Aware SCA

Is GHSA-hx78-272p-mqqh in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works