{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44965 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44965 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44965 is a medium-severity missing authorization vulnerability in Datadog Android App, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44965 and fix it if it is affected.\n\nWhat it is: CVE-2026-44965 is a medium-severity missing authorization vulnerability in Datadog Android App, published on 7 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44965 in the wild and no public exploit code.\n\nAffected product: Datadog Android App. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44965/ (Markdown: https://insights.sbomify.com/CVE-2026-44965/index.md)","id":"CVE-2026-44965","markdown":"https://insights.sbomify.com/CVE-2026-44965/index.md","name":"CVE-2026-44965","record":{"aliases":["GHSA-p6pw-xx6v-j4hh"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Datadog Android App","requires_auth":"none","summary":"A malicious app can brute-force widget IDs to launch exported activities, exposing live infrastructure data via a visual side channel.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-926","name":"Improper Export of Android Application Components"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Android App","id":"CVE-2026-44965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Velocity.js: Prototype Pollution in #set path assignment","id":"CVE-2026-44966"},"packages":[],"prev":{"headline":"Missing authorization in Android App","id":"CVE-2026-44964"},"products":["Android App"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-08","vendors":["Datadog"]},"summary":"A malicious app can brute-force widget IDs to launch exported activities, exposing live infrastructure data via a visual side channel.","url":"https://insights.sbomify.com/CVE-2026-44965/"}