Description
In versions of the Datadog Android application prior to v545-5.9.2, the app tags Crashlytics data with the user's Datadog UUID, with no user-facing opt-out.

Impact: The Datadog user UUID and crash data are visible within Firebase Crashlytics. This UUID is not identifying outside Datadog's own systems.
Published: 2026-08-07
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Datadog Android app includes a flaw that tags crash reports sent to Firebase Crashlytics with the user’s stable Datadog UUID, without providing a way for the user to opt out. Because the UUID is not publicly linked to other user data, the impact is limited to the disclosure of a stable identifier that could be used to link Crashlytics events to a specific user. The weakness is categorized as information disclosure (CWE‑200).

Affected Systems

Affecting the Datadog Android application, all releases prior to version v545‑5.9.2 are susceptible. Users who have installed those versions and allow Firebase Crashlytics to send crash data are at risk. The issue is present in every build that contains the Firebase Crashlytics integration and does not include an opt‑out mechanism for the UUID.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. No exploit vector or public exploit has been recorded, and the EPSS score is not available, which suggests a lower likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. Attackers would need access to Firebase Crashlytics logs to utilize the exposed UUID, so the threat is primarily privacy‑related rather than a direct compromise of code or data integrity.

Generated by OpenCVE AI on August 8, 2026 at 03:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Datadog Android application to v545‑5.9.2 or later, which removes the UUID from Crashlytics reports.
  • If an upgrade is not immediately possible, disable Firebase Crashlytics by removing its dependency from your build configuration or by disabling it in the Android manifest, ensuring no crash data is sent.
  • If disabling Crashlytics is not viable, contact Datadog support and request a patch or a configuration change that prevents the Datadog UUID from being included in Crashlytics payloads.

Generated by OpenCVE AI on August 8, 2026 at 03:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 08 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Datadog
Datadog android App
Vendors & Products Datadog
Datadog android App

Sat, 08 Aug 2026 02:45:00 +0000

Type Values Removed Values Added
Title Datadog Android App Sends Stable User Identifier to Firebase Crashlytics

Sat, 08 Aug 2026 02:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 08 Aug 2026 01:30:00 +0000

Type Values Removed Values Added
Description On every successful login, the Datadog Android application calls FirebaseCrashlytics.setUserId with the signed-in user's Datadog UUID — a stable per-user identifier that is meaningful inside Datadog. This associates the Datadog user UUID with the device's Firebase installation ID on Google'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. In versions of the Datadog Android application prior to v545-5.9.2, the app tags Crashlytics data with the user's Datadog UUID, with no user-facing opt-out. Impact: The Datadog user UUID and crash data are visible within Firebase Crashlytics. This UUID is not identifying outside Datadog's own systems.

Fri, 07 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Title Datadog Android App Sends Stable User Identifier to Firebase Crashlytics

Fri, 07 Aug 2026 18:15:00 +0000

Type Values Removed Values Added
Description On every successful login, the Datadog Android application calls FirebaseCrashlytics.setUserId with the signed-in user's Datadog UUID — a stable per-user identifier that is meaningful inside Datadog. This associates the Datadog user UUID with the device's Firebase installation ID on Google'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.
Weaknesses CWE-200
References

Subscriptions

Datadog Android App
cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published:

Updated: 2026-08-08T01:05:53.273Z

Reserved: 2026-05-19T15:00:09.319Z

Link: CVE-2026-47364

cve-icon Vulnrichment

Updated: 2026-08-07T18:34:50.582Z

cve-icon NVD

Status : Received

Published: 2026-08-07T18:17:17.217

Modified: 2026-08-08T02:17:17.890

Link: CVE-2026-47364

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-08T20:40:50Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor