CVE-2026-56995 · Other
NO FIX YET
Multiple locations allow corruption of host allocator metadata in shared memory, caused by a memory corruption flaw. A local attacker with System-level execution can escalate privileges, and no user interaction is needed.
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.
No product ranges from the sources yet.
Who cares android, shared-memory
Unknown from the sources.
No fix yet, per the sources.
In multiple locations, there is a possible way to corrupt host allocator metadata in shared memory due to memory corruption. This could lead to local escalation of privilege with System 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.