Advisory record · GHSA-c38f-wx89-p2xg

UltraJSON has a Memory Leak in ujson.dump() on Write Failure

CVSS 8.7 HighEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 12 May 2026, 22:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ujsonPyPI<5.12.15.12.1
Identifiers
GHSA-c38f-wx89-p2xg · CVE-2026-44660 · PYSEC-2026-2293
Weakness (CWE)
CWE-401
Published
12 May 2026
Updated
10 Sept 2026

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

Written 1 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.