<?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, 12 Oct 2026 18:17:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-270463</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-270463</link>
      <description>EUVD-2026-270463</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-270463</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27206</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27206</link>
      <description>&lt;p&gt;Zumba Json Serializer is a library to serialize PHP variables in JSON format. In versions 3.2.2 and below, the library allows deserialization of PHP objects from JSON using a special @type field. The deserializer instantiates any class specified in the @type field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application. If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as __wakeup() or __destruct()), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies. This behavior is similar in risk profile to PHP&amp;#39;s native unserialize() when used without the allowed_classes restriction. Applications are impacted only if untrusted or attacker-controlled JSON is passed into JsonSerializer::unserialize() and the application or its dependencies contain classes that can be leveraged as a gadget chain. This issue has been fixed in version 3.2.3. If an immediate upgrade isn&amp;#39;t feasible, mitigate the vulnerability by never deserializing untrusted JSON with JsonSerializer::unserialize(), validating and sanitizing all JSON input before deserialization, and disabling @type-based object instantiation wherever possible.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Zumba Json Serializer is a library to serialize PHP variables in JSON format. In versions 3.2.2 and below, the library allows deserialization of PHP objects from JSON using a special @type field. The deserializer instantiates any class specified in the @type field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application. If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as __wakeup() or __destruct()), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies. This behavior is similar in risk profile to PHP&amp;#39;s native unserialize() when used without the allowed_classes restriction. Applications are impacted only if untrusted or attacker-controlled JSON is passed into JsonSerializer::unserialize() and the application or its dependencies contain classes that can be leveraged as a gadget chain. This issue has been fixed in version 3.2.3. If an immediate upgrade isn&amp;#39;t feasible, mitigate the vulnerability by never deserializing untrusted JSON with JsonSerializer::unserialize(), validating and sanitizing all JSON input before deserialization, and disabling @type-based object instantiation wherever possible.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27206</guid>
    </item>
    <item>
      <title>GHSA-v7m3-fpcr-h7m2 — Zumba Json Serializer has a potential PHP Object Injection via Unrestricted @type in unserialize()</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v7m3-fpcr-h7m2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: zumba/json-serializer&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;The `zumba/json-serializer` library allows deserialization of PHP objects from JSON using a special `@type` field.&lt;/p&gt;
&lt;p&gt;Prior to version 3.2.3, the deserializer would instantiate any class specified in the `@type` field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application.&lt;/p&gt;
&lt;p&gt;If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as `__wakeup()` or `__destruct()`), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies.&lt;/p&gt;
&lt;p&gt;This behavior is similar in risk profile to PHP&amp;#39;s native `unserialize()` when used without the `allowed_classes` restriction.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability allows instantiation of arbitrary PHP classes via the `@type` field when deserializing JSON.&lt;/p&gt;
&lt;p&gt;Applications are impacted only if:
* Untrusted or attacker-controlled JSON is passed into `JsonSerializer::unserialize()`, and
* The application or its dependencies contain classes that can be leveraged as a gadget chain.&lt;/p&gt;
&lt;p&gt;Successful exploitation may lead to:
* Arbitrary code execution
* Data exfiltration
* File manipulation
* Denial of service&lt;/p&gt;
&lt;p&gt;Applications that only deserialize trusted data are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This issue is mitigated in version 3.2.3.&lt;/p&gt;
&lt;p&gt;Version 3.2.3 introduces the method:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: zumba/json-serializer&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;The `zumba/json-serializer` library allows deserialization of PHP objects from JSON using a special `@type` field.&lt;/p&gt;
&lt;p&gt;Prior to version 3.2.3, the deserializer would instantiate any class specified in the `@type` field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application.&lt;/p&gt;
&lt;p&gt;If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as `__wakeup()` or `__destruct()`), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies.&lt;/p&gt;
&lt;p&gt;This behavior is similar in risk profile to PHP&amp;#39;s native `unserialize()` when used without the `allowed_classes` restriction.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability allows instantiation of arbitrary PHP classes via the `@type` field when deserializing JSON.&lt;/p&gt;
&lt;p&gt;Applications are impacted only if:
* Untrusted or attacker-controlled JSON is passed into `JsonSerializer::unserialize()`, and
* The application or its dependencies contain classes that can be leveraged as a gadget chain.&lt;/p&gt;
&lt;p&gt;Successful exploitation may lead to:
* Arbitrary code execution
* Data exfiltration
* File manipulation
* Denial of service&lt;/p&gt;
&lt;p&gt;Applications that only deserialize trusted data are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;This issue is mitigated in version 3.2.3.&lt;/p&gt;
&lt;p&gt;Version 3.2.3 introduces the method:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v7m3-fpcr-h7m2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-27206</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27206</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-zumba-json-serializer, Ubuntu:25.10: php-zumba-json-serializer, Ubuntu:26.04:LTS: php-zumba-json-serializer&lt;/p&gt;
&lt;p&gt;Zumba Json Serializer is a library to serialize PHP variables in JSON format. In versions 3.2.2 and below, the library allows deserialization of PHP objects from JSON using a special @type field. The deserializer instantiates any class specified in the @type field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application. If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as __wakeup() or __destruct()), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies. This behavior is similar in risk profile to PHP&amp;#39;s native unserialize() when used without the allowed_classes restriction. Applications are impacted only if untrusted or attacker-controlled JSON is passed into JsonSerializer::unserialize() and the application or its dependencies contain classes that can be leveraged as a gadget chain. This issue has been fixed in version 3.2.3. If an immediate upgrade isn&amp;#39;t feasible, mitigate the vulnerability by never deserializing untrusted JSON with JsonSerializer::unserialize(), validating and sanitizing all JSON input before deserialization, and disabling @type-based object instantiation wherever possible.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: php-zumba-json-serializer, Ubuntu:25.10: php-zumba-json-serializer, Ubuntu:26.04:LTS: php-zumba-json-serializer&lt;/p&gt;
&lt;p&gt;Zumba Json Serializer is a library to serialize PHP variables in JSON format. In versions 3.2.2 and below, the library allows deserialization of PHP objects from JSON using a special @type field. The deserializer instantiates any class specified in the @type field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application. If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as __wakeup() or __destruct()), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies. This behavior is similar in risk profile to PHP&amp;#39;s native unserialize() when used without the allowed_classes restriction. Applications are impacted only if untrusted or attacker-controlled JSON is passed into JsonSerializer::unserialize() and the application or its dependencies contain classes that can be leveraged as a gadget chain. This issue has been fixed in version 3.2.3. If an immediate upgrade isn&amp;#39;t feasible, mitigate the vulnerability by never deserializing untrusted JSON with JsonSerializer::unserialize(), validating and sanitizing all JSON input before deserialization, and disabling @type-based object instantiation wherever possible.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27206</guid>
    </item>
  </channel>
</rss>
