# CVE-2026-57014: NXP NCI HAL out-of-bounds write in NFC initialization

Source: https://junglewise.ai/threats/cve-2026-57014-nxp-nci-hal-out-of-bounds-write-in-nfc-initialization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-57014 · Severity: high · CVSS 7.8 · Published 2026-09-15

The NXP NCI HAL (NFC controller interface) contains a missing bounds check in the NFC initialization response handler that allows an out-of-bounds write. An attacker with local access can exploit this vulnerability to gain elevated privileges on the device without requiring any special permissions or user interaction.

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

## Quick answers

**Is CVE-2026-57014 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-57014 being exploited in the wild.

**How severe is CVE-2026-57014?** High severity, with a CVSS score of 7.8, published 15 September 2026.

**Which products and versions are affected?** NXP NCI HAL <UNKNOWN>.

**Is there a fix for CVE-2026-57014?** A patch was published on 2026-09-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-57014 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-57014?** Check whether you run Google Android or NXP NCI HAL 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 exists in the phNxpNciHal_ext_process_nfc_init_rsp function in phNxpNciHal_ext.cc, where insufficient bounds validation on write operations allows an attacker to write data beyond allocated buffer boundaries. This is a classic out-of-bounds write vulnerability that enables local privilege escalation. The function processes NFC controller initialization responses and lacks proper size checks before writing response data to memory. An attacker with local access can trigger this condition to corrupt memory and escalate privileges on the device. Patches are available through the Android security bulletin dated 2026-09-05 or later.

## Affected products

- NXP NCI HAL <UNKNOWN>

## Timeline

- 2026-09-15: disclosed
- 2026-09-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-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)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-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)