<?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>Sat, 24 Oct 2026 00:09:30 +0000</lastBuildDate>
    <item>
      <title>BIT-parse-2021-41109 — LiveQuery publishes user session tokens</title>
      <link>https://cve.radiocsirt.org/vuln/bit-parse-2021-41109</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-parse-2021-41109</guid>
    </item>
    <item>
      <title>EUVD-2026-31498</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31498</link>
      <description>EUVD-2026-31498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31498</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41109</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41109</link>
      <description>&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41109</guid>
    </item>
    <item>
      <title>GHSA-7pr3-p5fm-8r9x — LiveQuery publishes user session tokens in parse-server</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7pr3-p5fm-8r9x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;### Impact
For regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.&lt;/p&gt;
&lt;p&gt;### Patches
Remove session token from LiveQuery payload.&lt;/p&gt;
&lt;p&gt;### Workaround
Set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;### Impact
For regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload.&lt;/p&gt;
&lt;p&gt;### Patches
Remove session token from LiveQuery payload.&lt;/p&gt;
&lt;p&gt;### Workaround
Set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7pr3-p5fm-8r9x</guid>
    </item>
    <item>
      <title>gsd-2021-41109</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41109</link>
      <description>gsd-2021-41109</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41109</guid>
    </item>
  </channel>
</rss>
