Skip to main content
VulnerabilityPublished

CVE-2025-11618: AWS FreeRTOS-Plus-TCP · NULL Pointer Dereference

Affects AWS FreeRTOS-Plus-TCPSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AWS FreeRTOS-Plus-TCPAffected
  • =4.0.0
Fixed in–

AI-suggested

  1. Upgrade all AWS FreeRTOS-Plus-TCP deployments to the latest version that includes the patch for CVE-2025-11618.
  2. Audit and patch any forks or derivative codebases that incorporate FreeRTOS-Plus-TCP to ensure the validation fix is applied.
  3. Implement network-level filtering to block malformed or suspicious IPv6 UDP packets, especially those with invalid IP version fields, to reduce exposure.
  4. Monitor device logs and network traffic for anomalies indicative of malformed packet attempts or crashes.
  5. Employ robust device management and update mechanisms to rapidly deploy patches across distributed IoT and embedded device fleets.
  6. Where feasible, segment IoT networks to limit exposure of vulnerable devices to untrusted networks.
  7. Conduct regular security assessments of embedded network stacks and protocol implementations to identify similar validation weaknesses early. These steps go beyond generic advice by focusing on patch management, network filtering, and proactive monitoring tailored to embedded IPv6 environments.

Description

A missing validation check in FreeRTOS-Plus-TCP's UDP/IPv6 packet processing code can lead to an invalid pointer dereference when receiving a UDP/IPv6 packet with an incorrect IP version field in the packet header. This issue only affects applications using IPv6. We recommend upgrading to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes.

References

Community reviews

Loading reviews…