Description
In versions of the Datadog Android application prior to v541-5.9.2, BubbleChatActivity is exported with no permission guard and accepts a SEND intent with a caller-supplied conversation_id. When the activity closes and no in-process session matches that ID, it unconditionally cancels notification ID 9201 (the Bits AI chat notification), with no check on the caller's identity or ownership of the conversation.
This requires a malicious application co-installed on the victim's device.
Impact: A co-installed application can silently dismiss the victim's Bits AI chat notification. No chat content is exposed; conversation data remains server-authentication gated and is never returned to the caller.
Published: 2026-08-07
Score: 6.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In versions of the Datadog Android application prior to v541-5.9.2, BubbleChatActivity is exported without a permission guard and accepts a SEND intent carrying a caller‑supplied conversation_id. When the activity terminates and no in‑process session matches that ID, it unconditionally cancels notification ID 9201 (the Bits AI chat notification) without verifying the caller’s identity or ownership of the conversation. A malicious co‑installed application can therefore launch this activity, causing the notification to disappear silently. No chat content is exposed; conversation data remains server‑authenticated and is never returned to the caller, so the impact is limited to the loss of the notification, which can inconvenience users or potentially aid phishing attempts within app workflows.

Affected Systems

Vendor Datadog; product Datadog Android App. All releases prior to v541‑5.9.2 are affected; the vulnerability is fixed in v541‑5.9.2 and subsequent versions.

Risk and Exploitability

This vulnerability is likely exploitable by any locally installed, zero‑permission application that can send a SEND intent, as inferred from the exported activity. The attacker needs only to co‑install a small third‑party app that fires the intent; no network connection or elevated privileges are required. The EPSS score is unavailable and the vulnerability is not listed in the KEV catalog. Because the attack path is straightforward and does not rely on user interaction with the notification itself, the risk of automated exploitation is moderate, though the practical effect is confined to the removal of a single notification.

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

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Install the latest Datadog Android application update that disables the exported BubbleChatActivity or adds proper permission checks.
  • Uninstall or disable any third‑party applications that may send SEND intents targeting the Datadog app to prevent exploitation.
  • If an immediate update is not possible, use device administration or app‑ops policies to block third‑party applications from starting exported activities or to restrict SEND intents, thereby mitigating the risk until a patch is available.

Generated by OpenCVE AI on August 8, 2026 at 02: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 03:15:00 +0000

Type Values Removed Values Added
Title Forced Removal of Bits AI Chat Notification in Datadog Android App

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

Type Values Removed Values Added
Description 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 conversation_id from Intent extras and, on onDestroy, calls BubbleChatNotification.dismiss whenever no active in-process session matches the caller-supplied conversation_id. 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 conversation_id. A zero-permission co-installed application can therefore launch BubbleChatActivity with any random conversation_id; 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). In versions of the Datadog Android application prior to v541-5.9.2, BubbleChatActivity is exported with no permission guard and accepts a SEND intent with a caller-supplied conversation_id. When the activity closes and no in-process session matches that ID, it unconditionally cancels notification ID 9201 (the Bits AI chat notification), with no check on the caller's identity or ownership of the conversation. This requires a malicious application co-installed on the victim's device. Impact: A co-installed application can silently dismiss the victim's Bits AI chat notification. No chat content is exposed; conversation data remains server-authentication gated and is never returned to the caller.

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

Type Values Removed Values Added
Title Forced Removal of Bits AI Chat Notification in Datadog Android App

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

Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

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


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

Type Values Removed Values Added
Description 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 conversation_id from Intent extras and, on onDestroy, calls BubbleChatNotification.dismiss whenever no active in-process session matches the caller-supplied conversation_id. 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 conversation_id. A zero-permission co-installed application can therefore launch BubbleChatActivity with any random conversation_id; 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).
Weaknesses CWE-926
References

Subscriptions

Datadog Android App
cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published:

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

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

Link: CVE-2026-47361

cve-icon Vulnrichment

Updated: 2026-08-07T18:31:44.403Z

cve-icon NVD

Status : Received

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

Modified: 2026-08-08T02:17:17.460

Link: CVE-2026-47361

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

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

Weaknesses
  • CWE-926

    Improper Export of Android Application Components