Quick answers
- Is CVE-2026-0177 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0177 being exploited in the wild.
- How severe is CVE-2026-0177?
- Medium severity, with a CVSS score of 4.4, published 15 September 2026.
- Which products and versions are affected?
- Google Pixel Devices All supported Pixel devices running OS versions prior to 2026-09-05 security patch.
- Is there a fix for CVE-2026-0177?
- A patch was published on 2026-09-05: Fixed in security patch level 2026-09-05 or later for all supported Pixel devices Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0177 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-0177?
- Check whether you run Google Android or Google Pixel Devices 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 an out-of-bounds read in the do_sss_aes_gcm_256_op function of crypto-aes.c in the Google Secure Server System (GSA) component. A missing bounds check on buffer operations allows an attacker with System execution privileges to read memory beyond allocated boundaries. The attack is local, requires no user interaction, and can disclose sensitive information maintained by the secure enclave or cryptographic subsystem. Patches are available in the 2026-09-05 Android security update for Pixel devices.
Affected products
- Google Pixel devices All supported Pixel devices running OS versions prior to 2026-09-05 security patch
Timeline
- 2026-09-15: disclosed: Published in Pixel Update Bulletin—September 2026
- 2026-09-05: patched: Fixed in security patch level 2026-09-05 or later for all supported Pixel devices