CVE-2026-47362: SQL Injection

Published Aug 7, 2026
·
Updated

The Datadog Android application stores operationally sensitive content in plaintext SQLite databases via Room. Two databases were reviewed: LocalNotificationDatabase (table localnotifications, columns including title, message, recipient, service, tags, and on-call/incident deeplinks) and SearchRecentDatabase (table searchrecents, storing every in-app search query the user typed). A repository-wide search for SQLCipher, SupportFactory, openHelperFactory, or any Room encryption configuration returns no matches. Databases are stored as cleartext SQLite files in /data/data/com.datadog.app/databases/. At-rest protection therefore depends solely on the Android application sandbox — the standard Android baseline, adequate for many applications but flagged here as a hardening recommendation because the stored content is operationally sensitive (customer infrastructure monitoring metadata, incident notification recipients, and free-text search queries that may reveal service names, dashboards, and queries of interest). Exploitation paths include rooted or jailbroken devices, adb backup if android:allowBackup is misconfigured for any build flavor, physical-device handover scenarios, and forensic acquisition.

Affected Software

1 affected component
Datadog Android application

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Change Room database configuration to store LocalNotificationDatabase and SearchRecentDatabase using an at-rest encryption mechanism instead of cleartext SQLite files located under /data/data/com.datadog.app/databases/.

    Datadog Android app (Room persistence) Database encryption at rest = Enabled (Room/SQLite encryption)
  2. Compensating control

    Harden against rooted/jailbroken and forensic acquisition scenarios by enforcing device integrity controls (e.g., block on rooted/jailbroken devices and restrict debugging/forensic access) because at-rest storage is currently plaintext in /data/data/com.datadog.app/databases/.

  3. Compensating control

    Verify and correct Android backup settings by ensuring android:allowBackup is not enabled for any build flavor, to reduce risk of adb backup/restore exposing plaintext SQLite databases.

Event History

Aug 7, 2026
CVE Published
via MITRE·06:02 PM
Data Sourced
via MITRE·06:02 PM
DescriptionWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47362?

CVE-2026-47362 has a risk rating of 37.

2

How does CVE-2026-47362 affect the Datadog Android application?

CVE-2026-47362 allows operationally sensitive content to be stored in plaintext SQLite databases, potentially exposing sensitive information.

3

What components of the Datadog Android application are impacted by CVE-2026-47362?

CVE-2026-47362 affects the LocalNotificationDatabase and the SearchReceivedDatabase.

4

How do I fix CVE-2026-47362 in the Datadog Android application?

To fix CVE-2026-47362, it is recommended to encrypt the SQLite databases used by the application.

5

What kind of data is at risk in CVE-2026-47362?

CVE-2026-47362 exposes operationally sensitive data like notification messages, recipient details, and on-call incident links.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203