CVE-2026-32875

UltraJSON has an integer overflow handling large indent leads to buffer overflow or infinite loop

HIGH
7.5
CVSS Score
Published: March 20, 2026 at 01:35 AM UTC
Updated: July 15, 2026 at 02:20 AM UTC
2 products affected across 2 vendorsUltrajsonUltrajson

Using ultrajson by ultrajson?

Get instant alerts when new vulnerabilities affect ultrajson - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
PoC

Description

UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Versions 5.10 through 5.11.0 are vulnerable to buffer overflow or infinite loop through large indent handling. ujson.dumps() crashes the Python interpreter (segmentation fault) when the product of the indent parameter and the nested depth of the input exceeds INT32_MAX. It can also get stuck in an infinite loop if the indent is a large negative number. Both are caused by an integer overflow/underflow whilst calculating how much memory to reserve for indentation. And both can be used to achieve denial of service. To be vulnerable, a service must call ujson.dump()/ujson.dumps()/ujson.encode() whilst giving untrusted users control over the indent parameter and not restrict that indentation to reasonably small non-negative values. A service may also be vulnerable to the infinite loop if it uses a fixed negative indent. An underflow always occurs for any negative indent when the input data is at least one level nested but, for small negative indents, the underflow is usually accidentally rectified by another overflow. This issue has been fixed in version 5.12.0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1.0 ≤ v < 5.12.0
Affected range stops below 5.12.0, so it looks safe — our inference, not a vendor statement
v < 5.12.0
Affected range stops below 5.12.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (6)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/ultrajson/ultrajson/security/advisories/GHSA-c8rr-9gxc-jprv
x_refsource_MISCIssue Tracking
Source: cverecord
https://github.com/ultrajson/ultrajson/issues/700
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-32875
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2449400

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-190CWE-787CWE-835

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card