CVE-2021-42836 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in github.com/tidwall/gjson. 2 public exploit references exist, so weaponization risk is real. A fix is available for github.com/tidwall/gjson — see the affected versions and patch details below.
Duplicate Advisory: ReDoS via crafted JSON input in GJSON
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-42836 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/tidwall/gjsonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-ppj4-34rq-v8j9. This link is maintained to preserve external references.
Original Description
GJSON <= 1.9.2 allows attackers to cause a redos via crafted JSON input.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/tidwall/gjson | all versions | 1.9.3go get github.com/tidwall/gjson@v1.9.3 |
Affected Products
gjsongjson_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tidwall/gjson, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/tidwall/gjson to 1.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-42836 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2021-42836 in your dependencies?
Find it across Go, including transitive dependencies.