Skip to main content
VulnerabilityPublished

CVE-2026-77236: FreeRTOS-Kernel · Out-of-bounds Write

Affects FreeRTOS-KernelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.3 High : upgrade to 11.3.1 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade freertos/FreeRTOS-Kernel to 11.3.1.

Affected software

ProductAffectedFixed in
FreeRTOSFreeRTOS-KernelAffected
  • >=10.2.0 <=11.3.0
Fixed in–
GitHubfreertos/FreeRTOS-Kernelpkg:github/freertos/FreeRTOS-KernelOther threatsAffected
  • <11.3.1
Fixed in
  • 11.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade FreeRTOS-Kernel to version 11.3.1 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the vendor advisory, but the description clearly states that upgrading to 11.3.1 or later fixes the issue. No additional mitigations are specified.

Description

Missing minimum size validation in secure context allocation in FreeRTOS-Kernel before 11.3.1 might allow local users to corrupt secure-world heap metadata via an out-of-bounds write with an undersized stack size parameter. To remediate this issue, users should upgrade to version 11.3.1 or later.

References

Community reviews

Loading reviews…