<?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>Fri, 02 Oct 2026 18:38:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281265</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281265</link>
      <description>EUVD-2026-281265</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281265</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5600</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5600</link>
      <description>&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to 
return all check-in events of a specific event in fact returns all 
check-in events belonging to the respective organizer. This allows an 
API consumer to access information for all other events under the same 
organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to 
return all check-in events of a specific event in fact returns all 
check-in events belonging to the respective organizer. This allows an 
API consumer to access information for all other events under the same 
organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5600</guid>
    </item>
    <item>
      <title>GHSA-wr8q-c73g-m7gp — pretix: API leaks check-in data between events of the same organizer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wr8q-c73g-m7gp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pretix&lt;/p&gt;
&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-in events belonging to the respective organizer. This allows an API consumer to access information for all other events under the same organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pretix&lt;/p&gt;
&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to return all check-in events of a specific event in fact returns all check-in events belonging to the respective organizer. This allows an API consumer to access information for all other events under the same organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wr8q-c73g-m7gp</guid>
    </item>
    <item>
      <title>PYSEC-2026-111</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-111</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pretix&lt;/p&gt;
&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to 
return all check-in events of a specific event in fact returns all 
check-in events belonging to the respective organizer. This allows an 
API consumer to access information for all other events under the same 
organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pretix&lt;/p&gt;
&lt;p&gt;A new API endpoint introduced in pretix 2025 that is supposed to 
return all check-in events of a specific event in fact returns all 
check-in events belonging to the respective organizer. This allows an 
API consumer to access information for all other events under the same 
organizer, even those they should not have access to.&lt;/p&gt;
&lt;p&gt;These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:&lt;/p&gt;
&lt;p&gt;{
  &amp;#34;id&amp;#34;: 123,
  &amp;#34;successful&amp;#34;: true,
  &amp;#34;error_reason&amp;#34;: null,
  &amp;#34;error_explanation&amp;#34;: null,
  &amp;#34;position&amp;#34;: 321,
  &amp;#34;datetime&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;list&amp;#34;: 456,
  &amp;#34;created&amp;#34;: &amp;#34;2020-08-23T09:00:00+02:00&amp;#34;,
  &amp;#34;auto_checked_in&amp;#34;: false,
  &amp;#34;gate&amp;#34;: null,
  &amp;#34;device&amp;#34;: 1,
  &amp;#34;device_id&amp;#34;: 1,
  &amp;#34;type&amp;#34;: &amp;#34;entry&amp;#34;
}&lt;/p&gt;
&lt;p&gt;An unauthorized user usually has no way to match these IDs (position) back to individual people.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-111</guid>
    </item>
  </channel>
</rss>
