Debian Package Tracker
Register | Log in
Subscribe

ujson

Choose email to subscribe with

general
  • source: ujson (main)
  • version: 5.11.0-3
  • maintainer: Debian Python Team (DMD)
  • uploaders: Mo Zhou [DMD]
  • arch: any
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 4.0.2-1
  • oldstable: 5.7.0-1
  • stable: 5.10.0-1
  • testing: 5.11.0-3
  • unstable: 5.11.0-3
versioned links
  • 4.0.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.7.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.10.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.11.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-ujson
action needed
Multiarch hinter reports 1 issue(s) high
There are issues with the multiarch metadata for this package.
  • python3-ujson conflicts on /usr/share/doc/python3-ujson/changelog.Debian.gz on loong64 <-> amd64, arm64, armhf and 4 more
Created: 2026-04-19 Last update: 2026-04-30 15:00
A new upstream version is available: 5.12.0 high
A new upstream version 5.12.0 is available, you should consider packaging it.
Created: 2026-03-14 Last update: 2026-04-30 12:18
2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:
  • CVE-2026-32874: UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Versions 5.4.0 through 5.11.0 contain an accumulating memory leak in JSON parsing large (outside of the range [-2^63, 2^64 - 1]) integers. The leaked memory is a copy of the string form of the integer plus an additional NULL byte. The leak occurs irrespective of whether the integer parses successfully or is rejected due to having more than sys.get_int_max_str_digits() digits, meaning that any sized leak per malicious JSON can be achieved provided that there is no limit on the overall size of the payload. Any service that calls ujson.load()/ujson.loads()/ujson.decode() on untrusted inputs is affected and vulnerable to denial of service attacks. This issue has been fixed in version 5.12.0.
  • CVE-2026-32875: 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.
Created: 2026-03-21 Last update: 2026-04-28 19:02
2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:
  • CVE-2026-32874: UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Versions 5.4.0 through 5.11.0 contain an accumulating memory leak in JSON parsing large (outside of the range [-2^63, 2^64 - 1]) integers. The leaked memory is a copy of the string form of the integer plus an additional NULL byte. The leak occurs irrespective of whether the integer parses successfully or is rejected due to having more than sys.get_int_max_str_digits() digits, meaning that any sized leak per malicious JSON can be achieved provided that there is no limit on the overall size of the payload. Any service that calls ujson.load()/ujson.loads()/ujson.decode() on untrusted inputs is affected and vulnerable to denial of service attacks. This issue has been fixed in version 5.12.0.
  • CVE-2026-32875: 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.
Created: 2026-03-21 Last update: 2026-04-28 19:02
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2026-32874: UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Versions 5.4.0 through 5.11.0 contain an accumulating memory leak in JSON parsing large (outside of the range [-2^63, 2^64 - 1]) integers. The leaked memory is a copy of the string form of the integer plus an additional NULL byte. The leak occurs irrespective of whether the integer parses successfully or is rejected due to having more than sys.get_int_max_str_digits() digits, meaning that any sized leak per malicious JSON can be achieved provided that there is no limit on the overall size of the payload. Any service that calls ujson.load()/ujson.loads()/ujson.decode() on untrusted inputs is affected and vulnerable to denial of service attacks. This issue has been fixed in version 5.12.0.
  • CVE-2026-32875: 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.
Created: 2026-03-21 Last update: 2026-04-28 19:02
2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:
  • CVE-2026-32874: UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Versions 5.4.0 through 5.11.0 contain an accumulating memory leak in JSON parsing large (outside of the range [-2^63, 2^64 - 1]) integers. The leaked memory is a copy of the string form of the integer plus an additional NULL byte. The leak occurs irrespective of whether the integer parses successfully or is rejected due to having more than sys.get_int_max_str_digits() digits, meaning that any sized leak per malicious JSON can be achieved provided that there is no limit on the overall size of the payload. Any service that calls ujson.load()/ujson.loads()/ujson.decode() on untrusted inputs is affected and vulnerable to denial of service attacks. This issue has been fixed in version 5.12.0.
  • CVE-2026-32875: 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.
Created: 2026-03-21 Last update: 2026-04-28 19:02
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).
Created: 2025-12-23 Last update: 2026-03-31 15:01
news
[rss feed]
  • [2025-12-03] ujson 5.11.0-3 MIGRATED to testing (Debian testing watch)
  • [2025-11-30] Accepted ujson 5.11.0-3 (source) into unstable (Alexandre Detiste)
  • [2025-10-13] ujson 5.11.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-10-10] Accepted ujson 5.11.0-2 (source) into unstable (Sophie Brun)
  • [2025-10-09] ujson 5.11.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-08-26] Accepted ujson 5.11.0-1 (source) into unstable (Mo Zhou)
  • [2024-05-21] ujson 5.10.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-05-19] Accepted ujson 5.10.0-1 (source) into unstable (Mo Zhou)
  • [2023-12-25] ujson 5.9.0-1 MIGRATED to testing (Debian testing watch)
  • [2023-12-20] Accepted ujson 5.9.0-1 (source) into unstable (Mo Zhou)
  • [2023-06-23] ujson 5.8.0-1 MIGRATED to testing (Debian testing watch)
  • [2023-06-17] Accepted ujson 5.8.0-1 (source) into unstable (Mo Zhou)
  • [2023-02-07] ujson 5.7.0-1 MIGRATED to testing (Debian testing watch)
  • [2023-02-01] Accepted ujson 5.7.0-1 (source) into unstable (Mo Zhou)
  • [2022-12-10] ujson 5.6.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-12-04] Accepted ujson 5.6.0-1 (source) into unstable (Mo Zhou)
  • [2022-10-22] ujson 5.5.0-2 MIGRATED to testing (Debian testing watch)
  • [2022-10-16] Accepted ujson 5.5.0-2 (source) into unstable (Jelmer Vernooij) (signed by: Jelmer Vernooij)
  • [2022-09-22] ujson 5.5.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-09-17] Accepted ujson 5.5.0-1 (source) into unstable (Mo Zhou)
  • [2022-07-13] ujson 5.4.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-07] Accepted ujson 5.4.0-1 (source) into unstable (Mo Zhou)
  • [2022-06-05] ujson 5.3.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-05-31] Accepted ujson 5.3.0-1 (source) into unstable (Mo Zhou)
  • [2022-04-15] ujson 5.2.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-04-08] Accepted ujson 5.2.0-1 (source) into unstable (Mo Zhou)
  • [2022-02-26] Accepted ujson 1.35-1+deb9u1 (source) into oldoldstable (Anton Gladky)
  • [2022-01-10] ujson 5.1.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-01-04] Accepted ujson 5.1.0-1 (source) into unstable (Mo Zhou)
  • [2021-11-18] ujson 4.2.0-1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 2
  • RC: 0
  • I&N: 1
  • M&W: 1
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 5.11.0-3build1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing