CVE-2026-59596 · Infrastructure
NO FIX YET
Several functions in mpu.c use an insecure default value, which lets code in non-secure memory execute inside the security coprocessor. An attacker with local access can escalate privileges without extra execution rights or 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 sources do not name the affected device, chip or firmware, so unknown. The flaw is local, so it matters only where an attacker already runs code on the device.
Who cares firmware, security-coprocessor
Unknown from the sources.
No fix yet, per the sources.
In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. 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.