CVE Intelligence
High Access control

CVE-2026-109587 — Incorrect authorization in the Arm Cortex-R82 MPU port in FreeRTOS-Kernel

Incorrect authorization in the Arm Cortex-R82 (Armv8-R AArch64) MPU port in FreeRTOS-Kernel V11.3.0 and V11.3.1 might allow an unprivileged task on MPU-enabled builds to read and write privileged kernel memory outside the regions assigned to it, via a buffer argument passed to an MPU system call. To remediate this issue, users should upgrade to version V11.3.2 or later.

Published Oct 16, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: AMZN

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Freertos
FreeRTOS-Kernel
CVSS base
8.8
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Freertos FreeRTOS-Kernel).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Freertos FreeRTOS-Kernel ≥ 11.3.0 and ≤ 11.3.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.3 CVSS 4.0 Critical — — ff89ba41-3aa1-4d27-914a-91399e9639e5 via NIST National Vulnerability Database
9.3 CVSS 4.0 Critical — — AMZN via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.0 6.0 ff89ba41-3aa1-4d27-914a-91399e9639e5 via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — AMZN via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: ff89ba41-3aa1-4d27-914a-91399e9639e5)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Audit administrative actions and access to resources outside each user’s normal pattern.
endpoint telemetry (EDR)authentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 16, 2026 · NIST National Vulnerability Database
  • Affected products added · freertos/freertos-kernel
    Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 16, 2026
  • CVSS changed · 8.8
    Oct 16, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 16, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 16, 2026 · Alertas do Telegram
  • CVE published
    Oct 16, 2026 · AMZN

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 16, 2026 – Oct 16, 2026
  • 1× Official description updated · Oct 16, 2026 – Oct 16, 2026

References

3 on the record

Elsewhere on this site

Freertos
every CVE for this vendor
Access control
same class
CWE-863
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-109588 Numeric truncation in the MPU buffer authorization check in FreeRTOS-Kernel 17h
  • CVE-2026-77234 Improper input validation in FreeRTOS-Kernel timer command handling Aug 21, 2026
  • CVE-2026-77235 Missing privilege check in SecureContext_FreeContext in FreeRTOS-Kernel Aug 21, 2026
  • CVE-2026-77236 Missing size validation in SecureContext_AllocateContext in FreeRTOS-Kernel Aug 21, 2026
  • CVE-2026-77237 Missing type validation in xQueueAddToSet in FreeRTOS-Kernel Aug 21, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-109587 is "Incorrect authorization in the Arm Cortex-R82 MPU port in FreeRTOS-Kernel", rated High. It affects FreeRTOS-Kernel (Freertos); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.