CVE-2026-95400 · Infrastructure
NO FIX YET
A bounds check is missing in the NFC hardware write routine StNfc_hal_write in hal_st21nfc.cc, allowing an out-of-bounds write into global memory. An attacker with local code execution can escalate privileges without user interaction.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The flaw sits in the ST21NFC NFC hardware abstraction layer, a component of devices using that NFC chip. Exposure depends on whether a device ships this code; the sources do not name affected builds or versions. Only a local attacker with code already running on the device is described.
Not affected if no-st21nfc-chip
Who cares android, nfc, st21nfc
Unknown from the sources.
No fix yet, per the sources.
In StNfc_hal_write of hal_st21nfc.cc, there is a possible way to trigger an out of bounds write into global memory due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.