<?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>Thu, 08 Oct 2026 14:52:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-354755</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354755</link>
      <description>EUVD-2026-354755</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354755</guid>
    </item>
    <item>
      <title>fkie_cve-2026-73655</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-73655</link>
      <description>&lt;p&gt;Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.2, addGoogleStrategy() in apps/webapp/app/services/googleAuth.server.ts passes a Google profile email to findOrCreateGoogleUser() in apps/webapp/app/models/user.server.ts without requiring Google&amp;#39;s email_verified assertion. When existingEmailUser &amp;amp;&amp;amp; !existingUser is true, the flow writes the new Google authIdentifier into the existing email-matched account and returns that user object, allowing an attacker-controlled Google profile with an unverified matching email to take over the account. This issue is fixed in version 4.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.2, addGoogleStrategy() in apps/webapp/app/services/googleAuth.server.ts passes a Google profile email to findOrCreateGoogleUser() in apps/webapp/app/models/user.server.ts without requiring Google&amp;#39;s email_verified assertion. When existingEmailUser &amp;amp;&amp;amp; !existingUser is true, the flow writes the new Google authIdentifier into the existing email-matched account and returns that user object, allowing an attacker-controlled Google profile with an unverified matching email to take over the account. This issue is fixed in version 4.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-73655</guid>
    </item>
  </channel>
</rss>
