GHSA-xq3c-8gqm-v648 — async-graphql

1. Detect

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

2. Fix

   Update async-graphql to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq3c-8gqm-v648 is resolved across your whole dependency graph.

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

4. How O3 protects you

   O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xq3c-8gqm-v648 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xq3c-8gqm-v648. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.