Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
UltraJSON (ujson) versions before 5.12.1 leak memory when ujson.dump() writes to a file-like object and the write call raises an exception, because the serialized string is never released. An attacker who can make a write to such a file-like object fail, for example by closing a connection mid-response in a web server that uses ujson.dump(), can cause memory use to grow steadily until resources are exhausted. Upgrade to ujson 5.12.1. As a workaround, replace ujson.dump(obj, file) with file.write(ujson.dumps(obj)).
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.7 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0042, the 36th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-c38f-wx89-p2xg
- OSV: GHSA-c38f-wx89-p2xg
- github.com/ultrajson/ultrajson/security/advisories/GHSA-c38f-wx89-p2xg
- nvd.nist.gov/vuln/detail/CVE-2026-44660
- github.com/ultrajson/ultrajson/commit/82af1d0ac01d09aa40c887b460d44b9d9f4bccd9
- github.com/ultrajson/ultrajson
- github.com/ultrajson/ultrajson/releases/tag/5.12.1