<?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>Sun, 18 Oct 2026 02:52:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-26339</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-26339</link>
      <description>EUVD-2026-26339</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-26339</guid>
    </item>
    <item>
      <title>fkie_cve-2021-29437</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-29437</link>
      <description>&lt;p&gt;ScratchOAuth2 is an Oauth implementation for Scratch. Any ScratchOAuth2-related data normally accessible and modifiable by a user can be read and modified by a third party. 1. Scratch user visits 3rd party site. 2. 3rd party site asks user for Scratch username. 3. 3rd party site pretends to be user and gets login code from ScratchOAuth2. 4. 3rd party site gives code to user and instructs them to post it on their profile. 5. User posts code on their profile, not knowing it is a ScratchOAuth2 login code. 6. 3rd party site completes login with ScratchOAuth2. 7. 3rd party site has full access to anything the user could do if they directly logged in. See referenced GitHub security advisory for patch notes and workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ScratchOAuth2 is an Oauth implementation for Scratch. Any ScratchOAuth2-related data normally accessible and modifiable by a user can be read and modified by a third party. 1. Scratch user visits 3rd party site. 2. 3rd party site asks user for Scratch username. 3. 3rd party site pretends to be user and gets login code from ScratchOAuth2. 4. 3rd party site gives code to user and instructs them to post it on their profile. 5. User posts code on their profile, not knowing it is a ScratchOAuth2 login code. 6. 3rd party site completes login with ScratchOAuth2. 7. 3rd party site has full access to anything the user could do if they directly logged in. See referenced GitHub security advisory for patch notes and workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-29437</guid>
    </item>
    <item>
      <title>gsd-2021-29437</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-29437</link>
      <description>gsd-2021-29437</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-29437</guid>
    </item>
  </channel>
</rss>
