<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T16:12:02.988689+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-281265</id>
    <title>EUVD-2026-281265</title>
    <updated>2026-10-02T16:12:03.051727+00:00</updated>
    <content>EUVD-2026-281265</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-281265"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5600</id>
    <title>fkie_cve-2026-5600</title>
    <updated>2026-10-02T16:12:03.051762+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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.</p>
<p>These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:</p>
<p>{
  "id": 123,
  "successful": true,
  "error_reason": null,
  "error_explanation": null,
  "position": 321,
  "datetime": "2020-08-23T09:00:00+02:00",
  "list": 456,
  "created": "2020-08-23T09:00:00+02:00",
  "auto_checked_in": false,
  "gate": null,
  "device": 1,
  "device_id": 1,
  "type": "entry"
}</p>
<p>An unauthorized user usually has no way to match these IDs (position) back to individual people.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-5600"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wr8q-c73g-m7gp</id>
    <title>GHSA-wr8q-c73g-m7gp — pretix: API leaks check-in data between events of the same organizer</title>
    <updated>2026-10-02T16:12:03.051804+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pretix</p>
<p>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.</p>
<p>These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:</p>
<p>{
  "id": 123,
  "successful": true,
  "error_reason": null,
  "error_explanation": null,
  "position": 321,
  "datetime": "2020-08-23T09:00:00+02:00",
  "list": 456,
  "created": "2020-08-23T09:00:00+02:00",
  "auto_checked_in": false,
  "gate": null,
  "device": 1,
  "device_id": 1,
  "type": "entry"
}</p>
<p>An unauthorized user usually has no way to match these IDs (position) back to individual people.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wr8q-c73g-m7gp"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-111</id>
    <title>PYSEC-2026-111</title>
    <updated>2026-10-02T16:12:03.051839+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pretix</p>
<p>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.</p>
<p>These records contain information on the time and result of every ticket scan as well as the ID of the matched ticket. Example:</p>
<p>{
  "id": 123,
  "successful": true,
  "error_reason": null,
  "error_explanation": null,
  "position": 321,
  "datetime": "2020-08-23T09:00:00+02:00",
  "list": 456,
  "created": "2020-08-23T09:00:00+02:00",
  "auto_checked_in": false,
  "gate": null,
  "device": 1,
  "device_id": 1,
  "type": "entry"
}</p>
<p>An unauthorized user usually has no way to match these IDs (position) back to individual people.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-111"/>
  </entry>
</feed>
