<?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>Wed, 07 Oct 2026 10:09:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-349478</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-349478</link>
      <description>EUVD-2026-349478</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-349478</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47364</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47364</link>
      <description>&lt;p&gt;In versions of the Datadog Android application prior to v545-5.9.2, the app tags Crashlytics data with the user&amp;#39;s Datadog UUID, with no user-facing opt-out.&#13;
&#13;
Impact: The Datadog user UUID and crash data are visible within Firebase Crashlytics. This UUID is not identifying outside Datadog&amp;#39;s own systems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In versions of the Datadog Android application prior to v545-5.9.2, the app tags Crashlytics data with the user&amp;#39;s Datadog UUID, with no user-facing opt-out.&#13;
&#13;
Impact: The Datadog user UUID and crash data are visible within Firebase Crashlytics. This UUID is not identifying outside Datadog&amp;#39;s own systems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47364</guid>
    </item>
    <item>
      <title>GHSA-9pjj-6mjx-mcc6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9pjj-6mjx-mcc6</link>
      <description>&lt;p&gt;On every successful login, the Datadog Android application calls FirebaseCrashlytics.setUserId with the signed-in user&amp;#39;s Datadog UUID — a stable per-user identifier that is meaningful inside Datadog. This associates the Datadog user UUID with the device&amp;#39;s Firebase installation ID on Google&amp;#39;s backend. Separately, uncaught exceptions are forwarded to Firebase Crashlytics via recordException, attaching stack traces (which may include internal class names, package names, in-flight data referenced by crash frames, and any breadcrumbs) to the same user UUID.
No visible consent gate or opt-out for Crashlytics tagging was identified in the reviewed code paths. No email, name, or organization data is forwarded to Crashlytics in the reviewed paths.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;On every successful login, the Datadog Android application calls FirebaseCrashlytics.setUserId with the signed-in user&amp;#39;s Datadog UUID — a stable per-user identifier that is meaningful inside Datadog. This associates the Datadog user UUID with the device&amp;#39;s Firebase installation ID on Google&amp;#39;s backend. Separately, uncaught exceptions are forwarded to Firebase Crashlytics via recordException, attaching stack traces (which may include internal class names, package names, in-flight data referenced by crash frames, and any breadcrumbs) to the same user UUID.
No visible consent gate or opt-out for Crashlytics tagging was identified in the reviewed code paths. No email, name, or organization data is forwarded to Crashlytics in the reviewed paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9pjj-6mjx-mcc6</guid>
    </item>
  </channel>
</rss>
