# CVE-2026-95400: ST NFC HAL out-of-bounds write in global memory

Source: https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-95400 · Severity: info · Published 2026-11-10

An NFC hardware abstraction layer (HAL) component in Android devices contains an out-of-bounds write vulnerability that allows attackers to write beyond allocated memory boundaries. A local attacker can exploit this flaw to escalate privileges without needing special permissions or user interaction, potentially gaining control over the device.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)
- [Android integer overflow denial of service in framework](https://junglewise.ai/threats/cve-2026-59611-in-multiple-locations-there-is-a-possible-way-to-trigger-a)