CVE-2026-44965

{"id": "CVE-2026-44965", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-44965", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-07T18:38:34.010393Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "affected": [{"source": "support@hackerone.com", "affectedData": [{"vendor": "Datadog", "product": "Android App", "versions": [{"status": "affected", "version": "5.9.2", "lessThan": "5.9.2", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-07T18:17:14.690", "references": [{"url": "https://cwe.mitre.org/data/definitions/926.html", "source": "support@hackerone.com"}, {"url": "https://developer.android.com/develop/ui/views/appwidgets/configuration", "source": "support@hackerone.com"}, {"url": "https://trust.datadoghq.com/?tcuUid=2e8b8fa5-39ca-43f4-9f6a-aeafafb440ef", "source": "support@hackerone.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "support@hackerone.com", "description": [{"lang": "en", "value": "CWE-926"}]}], "descriptions": [{"lang": "en", "value": "In versions of the Datadog Android application prior to v545-5.9.2, six App Widget configuration activities (IncidentWidgetActivity, MonitorSavedViewWidgetActivity, OnCallShiftsWidgetActivity, OnCallPagesWidgetActivity, SloWidgetActivity, DashboardWidgetActivity) are exported with no permission guard. Each accepts a caller-supplied AppWidgetManager.EXTRA_APPWIDGET_ID and, when no deep-link destination is resolved, uses it to load the matching widget's stored session and automatically log in as that user. Because Android widget IDs are small sequential integers, a co-installed application can brute-force this value to find one that matches a widget configured on the victim's device.\r\nThis requires:\r\nA malicious application co-installed on the victim's device.\r\nAt least one of the six widgets configured on the victim's home screen.\r\nAn active Datadog session cached locally.\r\nImpact: The matching configuration activity opens in the foreground under the victim's session and renders live infrastructure data. Exposure is limited to a visual side channel (e.g., screen recording or accessibility services); the calling application cannot programmatically read the rendered data."}, {"lang": "es", "value": "En versiones de la aplicaci\u00f3n Datadog para Android anteriores a la v545-5.9.2, seis actividades de configuraci\u00f3n de App Widget (IncidentWidgetActivity, MonitorSavedViewWidgetActivity, OnCallShiftsWidgetActivity, OnCallPagesWidgetActivity, SloWidgetActivity, DashboardWidgetActivity) se exportan sin una protecci\u00f3n de permisos. Cada una acepta un AppWidgetManager.EXTRA_APPWIDGET_ID proporcionado por el llamador y, cuando no se resuelve ning\u00fan destino de enlace profundo, lo utiliza para cargar la sesi\u00f3n almacenada del widget correspondiente e iniciar sesi\u00f3n autom\u00e1ticamente como ese usuario. Debido a que los ID de los widgets de Android son enteros secuenciales peque\u00f1os, una aplicaci\u00f3n co-instalada puede forzar por fuerza bruta este valor para encontrar uno que coincida con un widget configurado en el dispositivo de la v\u00edctima.\nEsto requiere:\nUna aplicaci\u00f3n maliciosa co-instalada en el dispositivo de la v\u00edctima.\nAl menos uno de los seis widgets configurados en la pantalla de inicio de la v\u00edctima.\nUna sesi\u00f3n activa de Datadog almacenada en cach\u00e9 localmente.\nImpacto: La actividad de configuraci\u00f3n correspondiente se abre en primer plano bajo la sesi\u00f3n de la v\u00edctima y renderiza datos de infraestructura en vivo. La exposici\u00f3n se limita a un canal lateral visual (por ejemplo, grabaci\u00f3n de pantalla o servicios de accesibilidad); la aplicaci\u00f3n llamadora no puede leer program\u00e1ticamente los datos renderizados."}], "lastModified": "2026-10-23T20:10:00.160", "sourceIdentifier": "support@hackerone.com"}