# CVE-2026-47364: Information disclosure in Android App

> The Datadog Android app exposes user UUIDs and crash data in Firebase Crashlytics without user opt-out, allowing unauthorized visibility of this information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 8 Aug 2026
- **Also known as:** GHSA-9pjj-6mjx-mcc6

## What is CVE-2026-47364?

CVE-2026-47364 is a medium-severity vulnerability in Datadog Android App, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-47364?


## How do I fix CVE-2026-47364?

No fix has been published for CVE-2026-47364 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47364 being exploited?

There is no known exploitation of CVE-2026-47364 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47364 and fix it if it is affected.

What it is: CVE-2026-47364 is a medium-severity vulnerability in Datadog Android App, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47364 in the wild and no public exploit code.

Affected product: Datadog Android App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47364/ (Markdown: https://insights.sbomify.com/CVE-2026-47364/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47364
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47364
- OSV: https://osv.dev/vulnerability/CVE-2026-47364

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47364/
Summaries are generated and may contain mistakes; the official description above is the record.