Skip to main content
VulnerabilityPublished

CVE-2025-11616: AWS FreeRTOS-Plus_TCP · Buffer Over-read

Affects AWS FreeRTOS-Plus_TCPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.3.4 when convenient.

Data as of 17 Nov 2026, 20:24 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (AMZN)CVSS 4.05.3
CNA (AMZN)CVSS 3.15.4
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.3.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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. 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 17 Nov 2026.

What to do

Upgrade AWS FreeRTOS-Plus_TCP to 4.3.4.

Affected software

ProductAffectedFixed in
AWSFreeRTOS-Plus_TCPAffected
  • >=4.0.0 <4.3.4
Fixed in
  • 4.3.4

AI-suggested

Users should upgrade to FreeRTOS-Plus_TCP version 4.3.4 or later to apply the official fix. Additionally, any forked or derivative codebases should be patched to incorporate the same validation improvements. No other mitigations are specified or required.

Description

CVE-2025-11616 is a medium severity vulnerability in AWS FreeRTOS-Plus_TCP affecting IPv6 applications. It involves a buffer over-read due to missing validation in ICMPv6 packet processing, which can occur when receiving certain smaller-than-expected ICMPv6 message types. The issue affects versions from 4.0.0 up to but not including 4.3.4. A fix is available in version 4.3.4.

References

Community reviews

Loading reviews…