Secure-heap corruption via undersized stack allocation
Published Aug 21, 2026 · Updated Aug 21, 2026
Out-of-bounds write in FreeRTOS Kernel 10.2.0 through 11.3.0 allows local users to corrupt Secure-world heap metadata. SecureContext_AllocateContext accepts an undersized secure-stack request, allocates too little memory, then writes the stack-overflow sentinel outside the buffer. Only ARMv8-M TrustZone applications using secure contexts are exposed; a Non-Secure task with low privileges can corrupt adjacent Secure-heap control structures, typically causing a crash or undefined behavior.
Summary
What happened
Out-of-bounds write in FreeRTOS Kernel 10.2.0 through 11.3.0 allows local users to corrupt Secure-world heap metadata. SecureContext_AllocateContext accepts an undersized secure-stack request, allocates too little memory, then writes the stack-overflow sentinel outside the buffer. Only ARMv8-M TrustZone applications using secure contexts are exposed; a Non-Secure task with low privileges can corrupt adjacent Secure-heap control structures, typically causing a crash or undefined behavior.
The record
- CVE
- CVE-2026-77236
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- FreeRTOS
- Product
- FreeRTOS Kernel
- Classifications
- CWE-787, CAPEC-100, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.2.0 <=11.3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo