Quick answers
- Is CVE-2026-95400 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95400 being exploited in the wild.
- How severe is CVE-2026-95400?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Google Android Pixel devices with security patch level before 2026-11-05; STMicroelectronics St21nfc Versions in Pixel devices before 2026-11-05 patch.
- Is there a fix for CVE-2026-95400?
- Yes: fixed in Pixel devices with Android security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95400 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-95400?
- Check whether you run Google Android or STMicroelectronics St21nfc 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.
How to fix
- Fixed in: Pixel devices with Android security patch level 2026-11-05 or later
Technical details
The vulnerability exists in StNfc_hal_write of hal_st21nfc.cc due to an incorrect bounds check that fails to validate write operations against global memory buffers. This is a local privilege escalation (EoP) via out-of-bounds memory write; the attack vector is local with no additional execution privileges required. Patches are available in Pixel security updates with patch level 2026-11-05 or later.
Affected products
- Google Android Pixel devices with security patch level before 2026-11-05
- STMicroelectronics st21nfc Versions in Pixel devices before 2026-11-05 patch
Timeline
- 2026-11-10: disclosed
- 2026-11-05: patched