GHSA-3pqg-4rqg-pg9g

1. Detect

   Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.antisamy:antisamy. 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.

2. Fix

   Update org.owasp.antisamy:antisamy to 1.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pqg-4rqg-pg9g 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 pinpoints whether GHSA-3pqg-4rqg-pg9g 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-3pqg-4rqg-pg9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.