<?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>Thu, 08 Oct 2026 06:41:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33942 — Saloon has insecure deserialization in AccessTokenAuthenticator (object injection / RCE)</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-33942</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; saloonphp saloon&lt;/p&gt;
&lt;p&gt;Saloon is a PHP library that gives users tools to build API integrations and SDKs. Versions prior to 4.0.0 used PHP&amp;#39;s unserialize() in AccessTokenAuthenticator::unserialize() to restore OAuth token state from cache or storage, with allowed_classes =&amp;gt; true. An attacker who can control the serialized string (e.g. by overwriting a cached token file or via another injection) can supply a serialized &amp;#34;gadget&amp;#34; object. When unserialize() runs, PHP instantiates that object and runs its magic methods (__wakeup, __destruct, etc.), leading to object injection. In environments with common dependencies (e.g. Monolog), this can be chained to remote code execution (RCE). The fix in version 4.0.0 removes PHP serialization from the AccessTokenAuthenticator class requiring users to store and resolve the authenticator manually.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; saloonphp saloon&lt;/p&gt;
&lt;p&gt;Saloon is a PHP library that gives users tools to build API integrations and SDKs. Versions prior to 4.0.0 used PHP&amp;#39;s unserialize() in AccessTokenAuthenticator::unserialize() to restore OAuth token state from cache or storage, with allowed_classes =&amp;gt; true. An attacker who can control the serialized string (e.g. by overwriting a cached token file or via another injection) can supply a serialized &amp;#34;gadget&amp;#34; object. When unserialize() runs, PHP instantiates that object and runs its magic methods (__wakeup, __destruct, etc.), leading to object injection. In environments with common dependencies (e.g. Monolog), this can be chained to remote code execution (RCE). The fix in version 4.0.0 removes PHP serialization from the AccessTokenAuthenticator class requiring users to store and resolve the authenticator manually.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-33942</guid>
    </item>
  </channel>
</rss>
