<?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>Tue, 06 Oct 2026 14:53:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-341934</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-341934</link>
      <description>EUVD-2026-341934</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-341934</guid>
    </item>
    <item>
      <title>fkie_cve-2026-18029</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-18029</link>
      <description>&lt;p&gt;Our payment integration with GiroCheckout did not properly validate 
payment status responses. An attacker could use a successful payment 
status response from one payment and supply it to the system for a 
different payment, gaining access to multiple valid tickets with only 
one payment.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Our payment integration with GiroCheckout did not properly validate 
payment status responses. An attacker could use a successful payment 
status response from one payment and supply it to the system for a 
different payment, gaining access to multiple valid tickets with only 
one payment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-18029</guid>
    </item>
    <item>
      <title>GHSA-f83j-v8r3-vfhv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f83j-v8r3-vfhv</link>
      <description>&lt;p&gt;Our payment integration with GiroCheckout did not properly validate 
payment status responses. An attacker could use a successful payment 
status response from one payment and supply it to the system for a 
different payment, gaining access to multiple valid tickets with only 
one payment.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Our payment integration with GiroCheckout did not properly validate 
payment status responses. An attacker could use a successful payment 
status response from one payment and supply it to the system for a 
different payment, gaining access to multiple valid tickets with only 
one payment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f83j-v8r3-vfhv</guid>
    </item>
  </channel>
</rss>
