CVE-2026-32875

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

Published

March 20, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jul 7, 2026
Patch available. Sources: github_commit, github, redhat.
redhatMentions a patch (unverified)

2449400 – (CVE-2026-32875) CVE-2026-32875 ultrajson: UltraJSON: Denial of Service via large indent parameter in JSON serialization

https://bugzilla.redhat.com/show_bug.cgi?id=2449400
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-32875
githubMentions a patch (unverified)

Integer overflow handling large indent leads to buffer overflow or infinite loop · Advisory · ultrajson/ultrajson · GitHub

https://github.com/ultrajson/ultrajson/security/advisories/GHSA-c8rr-9gxc-jprv
generic

ujson.dumps crashes when indent is large · Issue #700 · ultrajson/ultrajson · GitHub

https://github.com/ultrajson/ultrajson/issues/700
github_commit Patch Available

commit 486bd4553dc4 (ultrajson/ultrajson)

Patch available: ultrajson/ultrajson 5.12.0 (contains commit 486bd4553dc4)

https://github.com/ultrajson/ultrajson/commit/486bd4553dc471a1de11613bc7347a6b318e37ea

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-ujson (5.11.0-3ubuntu0.1) @ resolute2026-06-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ujson5.10.0-1 ... 5.9.0-1 (8 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ujson5.10.0-1, 5.11.0-1, 5.11.0-2, 5.11.0-3, 5.13.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ujson5.10.0-1, 5.11.0-1, 5.11.0-2, 5.11.0-3
  • every version up to 5.13.0-1: fixed in 5.13.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ujson5.1.0 ... 5.9.0 (11 versions)
  • 5.1.0 up to 5.12.0: fixed in 5.12.0
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-21 21:01 UTCOSV refresh
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-17 19:30 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-08 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 17:08 UTCOSV refresh
  6. 2026-09-02 14:11 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-09-01 04:39 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 14:17 UTCEPSS rescore
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:03 UTCEPSS rescore
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:05 UTCEG score recompute
  26. 2026-08-16 11:05 UTCVendor advisory
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 19:51 UTCVendor advisory
  30. 2026-08-14 07:16 UTCEG score recompute
  31. 2026-08-14 07:16 UTCVendor advisory
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 21:57 UTCEG score recompute
  34. 2026-08-12 21:57 UTCVendor advisory
  35. 2026-08-12 13:50 UTCEPSS rescore
  36. 2026-08-11 21:24 UTCEG score recompute
  37. 2026-08-11 21:24 UTCVendor advisory
  38. 2026-08-11 04:27 UTCEG score recompute
  39. 2026-08-11 04:27 UTCVendor advisory
  40. 2026-08-11 00:00 UTCEPSS rescore
  41. 2026-08-10 04:37 UTCVendor advisory
  42. 2026-08-09 17:43 UTCEG score recompute
  43. 2026-08-09 17:43 UTCVendor advisory
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 06:48 UTCEG score recompute
  46. 2026-08-09 06:48 UTCVendor advisory
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-08 04:12 UTCVendor advisory
  49. 2026-08-07 17:18 UTCEG score recompute
  50. 2026-08-07 17:18 UTCVendor advisory
  51. 2026-08-06 19:22 UTCEG score recompute
  52. 2026-08-06 19:22 UTCVendor advisory
  53. 2026-08-06 13:46 UTCEPSS rescore
  54. 2026-08-06 01:29 UTCEG score recompute
  55. 2026-08-06 01:29 UTCVendor advisory
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:38 UTCEPSS rescore
  59. 2026-08-04 00:38 UTCEG score recompute
  60. 2026-08-04 00:38 UTCVendor advisory
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-02 16:16 UTCEG score recompute
  63. 2026-08-02 16:16 UTCVendor advisory
  64. 2026-08-02 02:27 UTCEPSS rescore
  65. 2026-08-01 04:16 UTCEPSS rescore
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-27 14:13 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-24 14:17 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-32875?
CVE-2026-32875 is a high vulnerability published on March 20, 2026. 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…
When was CVE-2026-32875 disclosed?
CVE-2026-32875 was first published on March 20, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32875 actively exploited?
CVE-2026-32875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32875?
CVE-2026-32875 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32875?
A fix for CVE-2026-32875 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32875

Explore →

Is Your Infrastructure Affected by CVE-2026-32875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.