<?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>Mon, 16 Nov 2026 20:32:25 +0000</lastBuildDate>
    <item>
      <title>BREW-ansible-CVE-2026-114613 — MessagePack: Unbounded memory leak in msgpack C extension on strict_map_key validation failure</title>
      <link>https://cve.radiocsirt.org/vuln/brew-ansible-cve-2026-114613</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The msgpack-python C extension (`msgpack._cmsgpack`) leaks a decoded map value when deserialization rejects a key with `strict_map_key=True` (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both `unpackb()` and the streaming `Unpacker` API are affected. The pure-Python fallback does not exhibit this leak in the reported tests.&lt;/p&gt;
&lt;p&gt;The report measured approximately 4 MiB retained per failed parse and 100 MiB after 25 failed parses on Windows with Python 3.14 and msgpack 1.2.2. These are reporter-provided results.&lt;/p&gt;
&lt;p&gt;### Additional impact: stale parser-stack references&lt;/p&gt;
&lt;p&gt;The reference-ownership audit performed while fixing this leak found an
additional memory-safety issue in the streaming `Unpacker`.&lt;/p&gt;
&lt;p&gt;After `unpack()` completed a nested container, an inactive parser-stack slot
could retain a non-owning pointer to the decoded object. A subsequent `skip()`
could reactivate that slot. If parsing then failed, context cleanup treated the
stale pointer as an owned reference and decremented it.&lt;/p&gt;
&lt;p&gt;This corrupts the object&amp;#39;s reference count and can result in a use-after-free
or double `Py_DECREF` when its actual owners later release it.&lt;/p&gt;
&lt;p&gt;Although few users use this API, but those who do may experience crashes or unexpected errors due to a use-after-free.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `msgpack/unpack.h`, `unpack_callback_map_item()` rejects keys that are neither `str` n…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The msgpack-python C extension (`msgpack._cmsgpack`) leaks a decoded map value when deserialization rejects a key with `strict_map_key=True` (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both `unpackb()` and the streaming `Unpacker` API are affected. The pure-Python fallback does not exhibit this leak in the reported tests.&lt;/p&gt;
&lt;p&gt;The report measured approximately 4 MiB retained per failed parse and 100 MiB after 25 failed parses on Windows with Python 3.14 and msgpack 1.2.2. These are reporter-provided results.&lt;/p&gt;
&lt;p&gt;### Additional impact: stale parser-stack references&lt;/p&gt;
&lt;p&gt;The reference-ownership audit performed while fixing this leak found an
additional memory-safety issue in the streaming `Unpacker`.&lt;/p&gt;
&lt;p&gt;After `unpack()` completed a nested container, an inactive parser-stack slot
could retain a non-owning pointer to the decoded object. A subsequent `skip()`
could reactivate that slot. If parsing then failed, context cleanup treated the
stale pointer as an owned reference and decremented it.&lt;/p&gt;
&lt;p&gt;This corrupts the object&amp;#39;s reference count and can result in a use-after-free
or double `Py_DECREF` when its actual owners later release it.&lt;/p&gt;
&lt;p&gt;Although few users use this API, but those who do may experience crashes or unexpected errors due to a use-after-free.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `msgpack/unpack.h`, `unpack_callback_map_item()` rejects keys that are neither `str` n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-ansible-cve-2026-114613</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-NS64838 — MessagePack is the serializer implementation for Python msgpack</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ns64838</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: miniforge3&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the miniforge3 package. MessagePack is the serializer implementation for Python msgpack.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: miniforge3&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the miniforge3 package. MessagePack is the serializer implementation for Python msgpack.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ns64838</guid>
    </item>
    <item>
      <title>EUVD-2026-391796</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391796</link>
      <description>EUVD-2026-391796</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391796</guid>
    </item>
    <item>
      <title>fkie_cve-2026-114613</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-114613</link>
      <description>&lt;p&gt;MessagePack is the serializer implementation for Python msgpack.org. Prior to 1.2.3, the msgpack-python C extension (msgpack._cmsgpack) leaks a decoded map value when deserialization rejects a key with strict_map_key=True (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both unpackb() and the streaming Unpacker API are affected. The pure-Python fallback does not exhibit this leak in the reported tests. This issue is fixed in version 1.2.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;MessagePack is the serializer implementation for Python msgpack.org. Prior to 1.2.3, the msgpack-python C extension (msgpack._cmsgpack) leaks a decoded map value when deserialization rejects a key with strict_map_key=True (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both unpackb() and the streaming Unpacker API are affected. The pure-Python fallback does not exhibit this leak in the reported tests. This issue is fixed in version 1.2.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-114613</guid>
    </item>
    <item>
      <title>GHSA-j586-36cw-2gc2 — MessagePack: Unbounded memory leak in msgpack C extension on strict_map_key validation failure</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j586-36cw-2gc2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: msgpack&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The msgpack-python C extension (`msgpack._cmsgpack`) leaks a decoded map value when deserialization rejects a key with `strict_map_key=True` (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both `unpackb()` and the streaming `Unpacker` API are affected. The pure-Python fallback does not exhibit this leak in the reported tests.&lt;/p&gt;
&lt;p&gt;The report measured approximately 4 MiB retained per failed parse and 100 MiB after 25 failed parses on Windows with Python 3.14 and msgpack 1.2.2. These are reporter-provided results.&lt;/p&gt;
&lt;p&gt;### Additional impact: stale parser-stack references&lt;/p&gt;
&lt;p&gt;The reference-ownership audit performed while fixing this leak found an
additional memory-safety issue in the streaming `Unpacker`.&lt;/p&gt;
&lt;p&gt;After `unpack()` completed a nested container, an inactive parser-stack slot
could retain a non-owning pointer to the decoded object. A subsequent `skip()`
could reactivate that slot. If parsing then failed, context cleanup treated the
stale pointer as an owned reference and decremented it.&lt;/p&gt;
&lt;p&gt;This corrupts the object&amp;#39;s reference count and can result in a use-after-free
or double `Py_DECREF` when its actual owners later release it.&lt;/p&gt;
&lt;p&gt;Although few users use this API, but those who do may experience crashes or unexpected errors due to a use-after-free.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `msgpack/unpack.h`, `unpack_callback_map_item()` rejects keys that are neither `str` n…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: msgpack&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The msgpack-python C extension (`msgpack._cmsgpack`) leaks a decoded map value when deserialization rejects a key with `strict_map_key=True` (the default). Repeated malformed inputs can cause unbounded process memory growth and denial of service in applications that deserialize attacker-controlled MessagePack data. Both `unpackb()` and the streaming `Unpacker` API are affected. The pure-Python fallback does not exhibit this leak in the reported tests.&lt;/p&gt;
&lt;p&gt;The report measured approximately 4 MiB retained per failed parse and 100 MiB after 25 failed parses on Windows with Python 3.14 and msgpack 1.2.2. These are reporter-provided results.&lt;/p&gt;
&lt;p&gt;### Additional impact: stale parser-stack references&lt;/p&gt;
&lt;p&gt;The reference-ownership audit performed while fixing this leak found an
additional memory-safety issue in the streaming `Unpacker`.&lt;/p&gt;
&lt;p&gt;After `unpack()` completed a nested container, an inactive parser-stack slot
could retain a non-owning pointer to the decoded object. A subsequent `skip()`
could reactivate that slot. If parsing then failed, context cleanup treated the
stale pointer as an owned reference and decremented it.&lt;/p&gt;
&lt;p&gt;This corrupts the object&amp;#39;s reference count and can result in a use-after-free
or double `Py_DECREF` when its actual owners later release it.&lt;/p&gt;
&lt;p&gt;Although few users use this API, but those who do may experience crashes or unexpected errors due to a use-after-free.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `msgpack/unpack.h`, `unpack_callback_map_item()` rejects keys that are neither `str` n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j586-36cw-2gc2</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-114613 — MessagePack: Unbounded memory leak in msgpack C extension on strict_map_key validation failure</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-114613</link>
      <description>msrc_CVE-2026-114613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-114613</guid>
    </item>
    <item>
      <title>RHSA-2026:95872 — Red Hat Security Advisory: RHOAI 3.5.3 - Red Hat OpenShift AI</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:95872</link>
      <description>&lt;p&gt;markdown: python-markdown: Denial of Service via inefficient inline link parsing undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives @fastify/static: @fastify/static: Information disclosure via route guard bypass fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority undici: undici: Denial of Service via unrequested WebSocket subprotocol extract-zip: extract-zip: Arbitrary file write via symlink in archive encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal find-my-way: find-my-way: Denial of Service vulnerability in HTTP/2 server systeminformation: systeminformation: Arbitrary Command Execution via OS Command Injection mlflow: mlflow: Arbitrary file write via FileStore path traversal mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers nltk: NLTK: Information Disclosure via Symlink Sandbox Bypass github.com/klauspost/compress: klauspost/compress: Denial of Service via integer overflow in dictionary processing com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via excessively long JSON property names accelerate: Hugging Face Accelerate: Path Traversal and Denial of Service via weight_map brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation aiohttp: AIOHTTP: HTTP Request Smuggling via WebSocket Upgrade aiohttp: AIOHTTP: Denial of Ser…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;markdown: python-markdown: Denial of Service via inefficient inline link parsing undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives @fastify/static: @fastify/static: Information disclosure via route guard bypass fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority undici: undici: Denial of Service via unrequested WebSocket subprotocol extract-zip: extract-zip: Arbitrary file write via symlink in archive encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal find-my-way: find-my-way: Denial of Service vulnerability in HTTP/2 server systeminformation: systeminformation: Arbitrary Command Execution via OS Command Injection mlflow: mlflow: Arbitrary file write via FileStore path traversal mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers nltk: NLTK: Information Disclosure via Symlink Sandbox Bypass github.com/klauspost/compress: klauspost/compress: Denial of Service via integer overflow in dictionary processing com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via excessively long JSON property names accelerate: Hugging Face Accelerate: Path Traversal and Denial of Service via weight_map brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation aiohttp: AIOHTTP: HTTP Request Smuggling via WebSocket Upgrade aiohttp: AIOHTTP: Denial of Ser…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:95872</guid>
    </item>
  </channel>
</rss>
