GHSA-m9hw-7xfv-wqg7
Fix: jwadhams/json-logic-js@fadfa5dGHSA-m9hw-7xfv-wqg7 is a remote code execution vulnerability in json-logic-js. O3 Security confirms whether GHSA-m9hw-7xfv-wqg7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in json-logic-js
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
json-logic-jsnpmDescription
Versions of json-logic-js prior to 2.0.0 are vulnerable to Prototype Pollution. The method operation allows a malicious user to modify the prototype of Object through the method property name. This causes modification of any existing property that will exist on all objects and leads to Remote Code Execution.
The following rule creates a popup when run from a browser:
{
"method": [
{
"method": [
{
"var": "__proto__.constructor.is.__proto__"
},
"constructor",
[
"var x = 'SECURITY!'; console.log(x, window.fetch); alert(x)"
]
]
},
"call"
]
}
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | json-logic-js | all versions | 2.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json-logic-js. 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 json-logic-js to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9hw-7xfv-wqg7 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-m9hw-7xfv-wqg7 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-m9hw-7xfv-wqg7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m9hw-7xfv-wqg7 in your dependencies?
O3 detects GHSA-m9hw-7xfv-wqg7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.