CVE-2026-47361: Medium severity Datadog Android application vulnerability
BubbleChatActivity in the Datadog Android application is declared android:exported="true" with no permission guard and accepts a SEND intent with mimeType text/plain. The activity reads a conversationid from Intent extras and, on onDestroy, calls BubbleChatNotification.dismiss whenever no active in-process session matches the caller-supplied conversationid. BubbleChatNotification.dismiss unconditionally cancels notification ID 9201 — the hard-coded Bits AI chat notification — using NotificationManager.cancel, with no validation of the caller's identity or ownership of the supplied conversationid. A zero-permission co-installed application can therefore launch BubbleChatActivity with any random conversationid; when the activity is finished, the Bits AI chat notification is cancelled on the victim device. No data exposure: chat content is server-authentication gated and is never returned to the caller. Shortcut removal is scoped to the attacker-supplied conversation ID, which is a random string and is not reachable without prior knowledge. Impact is confined to denial of the Bits AI chat notification (a nuisance and a potential aid to phishing of in-app workflows).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47361?
The severity of CVE-2026-47361 is rated at 16.
What is CVE-2026-47361 about?
CVE-2026-47361 involves the BubbleChatActivity in the Datadog Android application being declared with android:exported="true" without a permission guard.
How do I fix CVE-2026-47361?
To fix CVE-2026-47361, ensure that BubbleChatActivity is not exported or add proper permission checks to control access.
What risks are associated with CVE-2026-47361?
CVE-2026-47361 poses a risk of unauthorized access to sensitive chat data due to improper export settings.
Which software is affected by CVE-2026-47361?
CVE-2026-47361 affects the Datadog Android application.