CVE-2026-47361 Overview
CVE-2026-47361 affects the Datadog Android application in versions prior to v541-5.9.2. The BubbleChatActivity component is exported without a permission guard and accepts a SEND intent containing a caller-supplied conversation_id. When the activity closes and no in-process session matches the supplied ID, the app unconditionally cancels notification ID 9201, which corresponds to the Bits AI chat notification. The application performs no check on the caller's identity or ownership of the conversation. A malicious application co-installed on the same device can silently dismiss the victim's Bits AI chat notification. The issue is classified under CWE-926: Improper Export of Android Application Components.
Critical Impact
A co-installed malicious application can silently dismiss the victim's Bits AI chat notification, though no chat content is exposed.
Affected Products
- Datadog Android application versions prior to v541-5.9.2
- BubbleChatActivity component (exported without permission guard)
- Bits AI chat notification subsystem (notification ID 9201)
Discovery Timeline
- 2026-08-07 - CVE-2026-47361 published to NVD
- 2026-08-08 - Last updated in NVD database
Technical Details for CVE-2026-47361
Vulnerability Analysis
The vulnerability resides in the Datadog Android application's BubbleChatActivity. Android activities marked as exported are reachable by any other application on the device unless a signature-level permission or explicit intent filter check restricts access. In this case, BubbleChatActivity accepts an inbound SEND intent that includes an attacker-controlled conversation_id extra.
When the activity finishes, the application checks whether an in-process session matches the supplied conversation_id. If no match is found, the code path falls through to a cleanup routine that cancels notification 9201, which the Bits AI chat feature uses to surface pending messages. The cancellation runs regardless of which application initiated the intent.
Exploitation requires a second, malicious application already installed on the victim's device. The impact is limited to notification suppression. Conversation content stays server-authentication gated and is never returned to the caller through the intent response.
Root Cause
The root cause is improper export of an Android application component [CWE-926]. BubbleChatActivity is declared with android:exported="true" and lacks a permission attribute or runtime caller verification. The cleanup handler treats a missing session as a signal to dismiss the associated notification without validating that the caller owns the referenced conversation.
Attack Vector
A malicious co-installed application crafts an Intent with action SEND, targets the exported BubbleChatActivity, and sets conversation_id to any value that will not match an active in-process session. Starting the activity triggers the finish path, which cancels notification 9201. The attacker application requires no special Android permissions to reach the exported component. See the Datadog Trust Resource for vendor advisories.
// No verified proof-of-concept code is available.
// The attack pattern involves an Android Intent targeting the exported
// BubbleChatActivity component with a crafted conversation_id extra.
Detection Methods for CVE-2026-47361
Indicators of Compromise
- Unexpected dismissal of Bits AI chat notifications on managed Android devices running vulnerable Datadog client versions.
- Presence of untrusted third-party applications that issue Intent actions targeting com.datadog package components.
- Android logcat entries showing external callers invoking BubbleChatActivity outside normal in-app navigation.
Detection Strategies
- Inventory managed Android devices to identify installations of the Datadog application prior to v541-5.9.2.
- Use mobile threat defense telemetry to flag applications that enumerate or invoke exported activities of other installed packages.
- Review Android package manifests during mobile application vetting to identify components exported without permission guards.
Monitoring Recommendations
- Correlate mobile device management (MDM) inventory data with the fixed version threshold to track patch adoption.
- Monitor user reports of missing or silently dismissed Bits AI notifications as a behavioral signal.
- Review Android application sideloading events, which increase exposure to co-installed malicious applications.
How to Mitigate CVE-2026-47361
Immediate Actions Required
- Update the Datadog Android application to v541-5.9.2 or later on all managed devices.
- Enforce application update policies through MDM to prevent regression to vulnerable builds.
- Restrict installation of applications from untrusted sources on devices that access Datadog workloads.
Patch Information
Datadog resolved the issue in Datadog Android application v541-5.9.2. The fix adds caller validation before the notification cancellation path executes. Consult the Datadog Trust Resource for advisory details and release notes.
Workarounds
- Remove untrusted third-party applications from devices running vulnerable Datadog client versions.
- Limit device use to a curated set of enterprise-approved applications through MDM allowlists.
- Educate users to report any unexplained loss of Bits AI chat notifications for investigation.
# Verify installed Datadog Android application version via ADB
adb shell dumpsys package com.datadog.android | grep versionName
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
