Quick answers
- Is CVE-2026-49921 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49921 being exploited in the wild.
- How severe is CVE-2026-49921?
- Critical severity, with a CVSS score of 9.8, published 8 September 2026.
- Which products and versions are affected?
- Google Android 14 through 17.
- Is there a fix for CVE-2026-49921?
- A patch was published on 2026-09-05: Security patch level 2026-09-05 or later addresses the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49921 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-49921?
- Check whether you run Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a heap buffer overflow in multiple locations within Android's System component. The defect allows remote code execution (RCE) with no additional execution privileges needed and does not require user interaction for exploitation. The attack vector is network-based, and the flaw can be triggered through normal device operation or network communication. Patches have been released and are available in Android Security Patch Level 2026-09-05 and later, with fixes backported to AOSP versions 14, 15, 16, 16-qpr2, and 17.
Affected products
- Google Android 14 through 17
Timeline
- 2026-09-08: disclosed: Android Security Bulletin published
- 2026-09-05: patched: Security patch level 2026-09-05 or later addresses the vulnerability