<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 13:55:24 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-04296</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-04296</link>
      <description>bdu:2022-04296</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-04296</guid>
    </item>
    <item>
      <title>BREW-theharvester-CVE-2022-31116 — Incorrect handling of invalid surrogate pair characters</title>
      <link>https://cve.radiocsirt.org/vuln/brew-theharvester-cve-2022-31116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: theharvester&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: theharvester&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-theharvester-cve-2022-31116</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0366 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;les produits IBM&lt;/span&gt;. Certaines d'entre el…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0366</link>
      <description>certfr-2024-avi-0366</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0366</guid>
    </item>
    <item>
      <title>EUVD-2026-232682</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232682</link>
      <description>EUVD-2026-232682</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232682</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31116</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31116</link>
      <description>&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31116</guid>
    </item>
    <item>
      <title>GHSA-wpqr-jcpx-745r — Incorrect handling of invalid surrogate pair characters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wpqr-jcpx-745r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ujson&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ujson&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wpqr-jcpx-745r</guid>
    </item>
    <item>
      <title>gsd-2022-31116</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31116</link>
      <description>gsd-2022-31116</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31116</guid>
    </item>
    <item>
      <title>OESA-2026-3606 — python-ujson security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3606</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: python-ujson&lt;/p&gt;
&lt;p&gt;UltraJSON&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;UltraJSON (aka ujson) through 5.1.0 has a stack-based buffer overflow in Buffer_AppendIndentUnchecked (called from encode). Exploitation can, for example, use a large amount of indentation.(CVE-2021-45958)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;amp;apos;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.(CVE-2022-31116)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. In versions prior to 5.4.0 an error occurring while reallocating a buffer for string decoding can cause the buffer to get freed twice. Due to how UltraJSON uses the internal decoder, this double free is impossible to trigger from Python. This issue has been resolved in version 5.4.0 and all users should upgrade to UltraJSON 5.4.0. There are no known workarounds for this issue.(CVE-2022-31117)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C wi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: python-ujson&lt;/p&gt;
&lt;p&gt;UltraJSON&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;UltraJSON (aka ujson) through 5.1.0 has a stack-based buffer overflow in Buffer_AppendIndentUnchecked (called from encode). Exploitation can, for example, use a large amount of indentation.(CVE-2021-45958)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;amp;apos;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.(CVE-2022-31116)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. In versions prior to 5.4.0 an error occurring while reallocating a buffer for string decoding can cause the buffer to get freed twice. Due to how UltraJSON uses the internal decoder, this double free is impossible to trigger from Python. This issue has been resolved in version 5.4.0 and all users should upgrade to UltraJSON 5.4.0. There are no known workarounds for this issue.(CVE-2022-31117)&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C wi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3606</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:12183-1 — python310-ujson-5.4.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:12183-1</link>
      <description>&lt;p&gt;python310-ujson-5.4.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python310-ujson-5.4.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:12183-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-1057 — Incorrect handling of invalid surrogate pair characters</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1057</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ujson&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ujson&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;Anyone parsing JSON from an untrusted source is vulnerable.&lt;/p&gt;
&lt;p&gt;JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;p&gt;```python
# An unpaired high surrogate character is ignored.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;hello&amp;#39;&lt;/p&gt;
&lt;p&gt;# An unpaired low surrogate character is preserved.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;&lt;/p&gt;
&lt;p&gt;# A pair of surrogates with additional non surrogate characters pair up in spite of being invalid.
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;foo bar𐀀&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Users should upgrade to UltraJSON 5.4.0.&lt;/p&gt;
&lt;p&gt;From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output:&lt;/p&gt;
&lt;p&gt;```python3
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800&amp;#34;&amp;#39;)
&amp;#39;\ud800&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800hello&amp;#34;&amp;#39;)
&amp;#39;\ud800hello&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uDC00&amp;#34;&amp;#39;)
&amp;#39;\udc00&amp;#39;
&amp;gt;&amp;gt;&amp;gt; ujson.loads(r&amp;#39;&amp;#34;\uD800foo bar\uDC00&amp;#34;&amp;#39;)
&amp;#39;\ud800foo bar\udc00&amp;#39;
```&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;Short of switching to an entirely different JSON library, there are no safe alternatives to upgrading.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1057</guid>
    </item>
    <item>
      <title>RHSA-2022:8850 — Red Hat Security Advisory: Red Hat OpenStack Platform 16.2.4 (python-ujson) security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:8850</link>
      <description>&lt;p&gt;python-ujson: improper decoding of escaped surrogate characters may lead to string corruption, key confusion or value overwriting python-ujson: Potential double free of buffer during string decoding&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python-ujson: improper decoding of escaped surrogate characters may lead to string corruption, key confusion or value overwriting python-ujson: Potential double free of buffer during string decoding&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:8850</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-31116</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: pandas, Ubuntu:Pro:16.04:LTS: ujson, Ubuntu:16.04:LTS: collada2gltf, Ubuntu:16.04:LTS: pandas, Ubuntu:18.04:LTS: collada2gltf, Ubuntu:18.04:LTS: pandas, Ubuntu:Pro:18.04:LTS: ujson, Ubuntu:20.04:LTS: pandas, Ubuntu:22.04:LTS: collada2gltf, Ubuntu:22.04:LTS: pandas and 4 more&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: pandas, Ubuntu:Pro:16.04:LTS: ujson, Ubuntu:16.04:LTS: collada2gltf, Ubuntu:16.04:LTS: pandas, Ubuntu:18.04:LTS: collada2gltf, Ubuntu:18.04:LTS: pandas, Ubuntu:Pro:18.04:LTS: ujson, Ubuntu:20.04:LTS: pandas, Ubuntu:22.04:LTS: collada2gltf, Ubuntu:22.04:LTS: pandas and 4 more&lt;/p&gt;
&lt;p&gt;UltraJSON is a fast JSON encoder and decoder written in pure C with bindings for Python 3.7+. Affected versions were found to improperly decode certain characters. JSON strings that contain escaped surrogate characters not part of a proper surrogate pair were decoded incorrectly. Besides corrupting strings, this allowed for potential key confusion and value overwriting in dictionaries. All users parsing JSON from untrusted sources are vulnerable. From version 5.4.0, UltraJSON decodes lone surrogates in the same way as the standard library&amp;#39;s `json` module does, preserving them in the parsed output. Users are advised to upgrade. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31116</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-2265 — Red Hat OpenStack: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2265</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenStack ausnutzen, um die Verfügbarkeit, Vertraulichkeit und Integrität zu gefährden.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenStack ausnutzen, um die Verfügbarkeit, Vertraulichkeit und Integrität zu gefährden.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-2265</guid>
    </item>
  </channel>
</rss>
