How severe is GHSA-74cr-77xc-8g6r?

GHSA-74cr-77xc-8g6r has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-74cr-77xc-8g6r?

GHSA-74cr-77xc-8g6r affects the following packages: @apollo/gateway (npm). Ecosystems affected: npm.

How do I fix GHSA-74cr-77xc-8g6r?

Update @apollo/gateway to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74cr-77xc-8g6r is resolved across your whole dependency graph.

How do I detect GHSA-74cr-77xc-8g6r in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/gateway. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-74cr-77xc-8g6r 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.

How does O3 Security protect against GHSA-74cr-77xc-8g6r?

O3 pinpoints whether GHSA-74cr-77xc-8g6r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-74cr-77xc-8g6r actively exploited in the wild?

No public exploit code has been indexed for GHSA-74cr-77xc-8g6r 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-74cr-77xc-8g6r published, and has it been updated?

GHSA-74cr-77xc-8g6r was published on June 13, 2019 and was last updated on August 16, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-74cr-77xc-8g6r

HIGH

GHSA-74cr-77xc-8g6r is a high-severity (CVSS 7.3) remote code execution vulnerability in @apollo/gateway. O3 Security confirms whether GHSA-74cr-77xc-8g6r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in @apollo/gateway

Published

Jun 13, 2019

Updated

Aug 16, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@apollo/gatewaynpm

310Kdownloads / week

Description

Versions of @apollo/gateway prior to 0.6.2 are vulnerable to Prototype Pollution. The package uses deepMerge() to merge objects, which may allow attackers to alter the Object prototype through queries with GraphQL aliases. Carefully constructed payloads can override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.

Recommendation

Upgrade to version 0.6.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@apollo/gateway`	all versions	0.6.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/gateway. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @apollo/gateway to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74cr-77xc-8g6r 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.
How O3 protects you
O3 pinpoints whether GHSA-74cr-77xc-8g6r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-74cr-77xc-8g6r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `@apollo/gateway` prior to 0.6.2 are vulnerable to Prototype Pollution. The package uses deepMerge() to merge objects, which may allow attackers to alter the Object prototype through queries with GraphQL aliases. Carefully constructed payloads can override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution. ## Recommendation Upgrade to version 0.6.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-74cr-77xc-8g6r in your dependencies?

O3 detects GHSA-74cr-77xc-8g6r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works