<?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://db.gcve.eu</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, 15 Oct 2026 17:01:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-109954</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-109954</link>
      <description>&lt;p&gt;Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client&amp;#39;s transactional batch request interfere with other clients&amp;#39; database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients&amp;#39; acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client&amp;#39;s transactional batch request interfere with other clients&amp;#39; database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients&amp;#39; acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-109954</guid>
    </item>
    <item>
      <title>GHSA-jq9m-gc39-vm65</title>
      <link>https://db.gcve.eu/vuln/ghsa-jq9m-gc39-vm65</link>
      <description>&lt;p&gt;Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client&amp;#39;s transactional batch request interfere with other clients&amp;#39; database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients&amp;#39; acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client&amp;#39;s transactional batch request interfere with other clients&amp;#39; database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients&amp;#39; acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jq9m-gc39-vm65</guid>
    </item>
  </channel>
</rss>
