Skip to main content

Datadog Android CVE-2026-44965

| EUVDEUVD-2026-54571 MEDIUM
Improper Export of Android Application Components (CWE-926)
2026-08-07 support@hackerone.com GHSA-p6pw-xx6v-j4hh
5.5
CVSS 3.1 · Vendor: hackerone
Share

Severity by source

Vendor (hackerone) PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
vuln.today AI
3.3 LOW

AV:L for device-local co-installed app vector; C:L for visual-only session data disclosure; A:N because no availability impact exists despite the supplied vector's erroneous A:H.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:L/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (hackerone).

CVSS VectorVendor: hackerone

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Aug 07, 2026 - 20:58 vuln.today
Patch available
Aug 07, 2026 - 19:02 EUVD
CVE Published
Aug 07, 2026 - 18:17 cve.org
MEDIUM 5.5
CVE Published
Aug 07, 2026 - 18:17 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Six Android App Widget configuration activities in the Datadog Android application are declared android:exported="true" with no permission guard: IncidentWidgetActivity, MonitorSavedViewWidgetActivity, OnCallShiftsWidgetActivity, OnCallPagesWidgetActivity, SloWidgetActivity, and DashboardWidgetActivity. All six extend a shared base WidgetActivity that reads AppWidgetManager.EXTRA_APPWIDGET_ID from Intent extras and, when no resolved deep-link destination is supplied, uses that caller-controlled widget ID to look up the stored widget definition, fetch the associated user session, and perform an automatic login with source UserSessionSourceLogin.Automatic. Android App Widget IDs are small sequential integers assigned by AppWidgetManager. A zero-permission co-installed application can brute-force them by launching any of the six configuration activities with EXTRA_APPWIDGET_ID set to 1..N until one matches a configured widget on the victim device. When a match occurs, the activity foregrounds with the victim's session already loaded and renders the widget configuration UI, which is backed by live data pickers (SLOs, dashboards, incident severities and types, on-call pages and shifts) fetched through the victim's authenticated HTTP client. Exfiltration is screen-visible only - programmatic return of data to the caller is not possible from these activities. Disclosure is therefore a visual side-channel: accessibility services, screen recording, or screenshot capture. Preconditions: a malicious co-installed application, at least one of the six widgets configured on the victim's home screen, and an active Datadog session cached locally.

AnalysisAI

Six exported Android App Widget configuration activities in the Datadog Android application (versions prior to 5.9.2) allow a co-installed zero-permission malicious app to brute-force sequential App Widget IDs and trigger automatic Datadog session login for the victim, exposing live operational data - dashboards, SLOs, on-call schedules, incident details - as a visual side-channel. Exploitation is constrained by three simultaneous preconditions and data exfiltration is limited to screen-visible disclosure only, with no programmatic return path. No public exploit has been identified at time of analysis; SSVC rates exploitation as none with partial technical impact.

Technical ContextAI

Android's component export model allows any installed application to start an Activity declared android:exported='true' with no android:permission guard (CWE-926: Improper Export of Android Application Components). All six affected activities - IncidentWidgetActivity, MonitorSavedViewWidgetActivity, OnCallShiftsWidgetActivity, OnCallPagesWidgetActivity, SloWidgetActivity, and DashboardWidgetActivity - extend a shared base WidgetActivity that reads AppWidgetManager.EXTRA_APPWIDGET_ID directly from the calling Intent extras without validating the caller's identity. App Widget IDs are small sequential integers assigned by AppWidgetManager (not UUIDs or cryptographically random values), making brute-force enumeration trivial for any co-installed app. When the base activity resolves no deep-link destination, it uses the caller-supplied ID to fetch the stored widget definition and performs an automatic login with source UserSessionSourceLogin.Automatic, effectively handing the caller an authenticated session view. The data then surfaces through live authenticated API calls to Datadog endpoints backed by the victim's HTTP client.

RemediationAI

Upgrade the Datadog Android application to version 5.9.2 or later, which is confirmed as patching the improper activity exports per EUVD-2026-54571 and the Datadog Trust Center advisory at https://trust.datadoghq.com/?tcuUid=2e8b8fa5-39ca-43f4-9f6a-aeafafb440ef. As a compensating control pending upgrade, users should remove all six affected Datadog App Widgets from their home screens - this eliminates the required precondition that a configured widget exist, rendering the brute-force attack inert even if a malicious app is present. Enterprise MDM administrators (Intune, Jamf, etc.) should enforce app allowlisting to prevent co-installation of unvetted applications on managed devices, which removes the initial attacker foothold. Restricting sideloading via Android enterprise policy (disallowInstallUnknownSources) provides defense-in-depth but does not protect against Play Store-distributed malicious apps.

Share

CVE-2026-44965 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy