// Security Advisory Triage

FreeRTOS-Plus-TCP ≤V4.4.1 vulnerable to IPv6 RA spoofing and DNS cache poisoning

AWS security bulletins · published 2026-10-17 04:29 UTC
CORRECTED 2026-10-17 18:48 UTC — Correction, 17 October 2026: Our original advice omitted the fixed version and an additional configuration requirement for CVE-2026-102552. AWS’s current bulletin requires upgrading FreeRTOS-Plus-TCP to V4.4.2 and enabling ipconfigDNS_CHECK_REPLY_SOURCE_IP in FreeRTOSIPConfig.h. Source-IP checking is disabled by default, so upgrading alone does not remediate the DNS issue. Disabling IPv6 Router Advertisement processing is a workaround for CVE-2026-102551 only; it does not fix CVE-2026-102552. This clarification is based on the AWS bulletin retrieved on 17 October 2026. RADAR’s retained RSS capture lacked the remediation sections. We have not established whether the full AWS page contained these exact instructions when that RSS entry was captured.
Stood 14h 19m · cause writer overreach · every correction ↗
ACTION NEEDED VERIFY_EXPOSURE SECURITYAPI
WHAT CHANGEDAWS disclosed CVE-2026-102551 and CVE-2026-102552 in FreeRTOS-Plus-TCP versions V4.4.1 and earlier on 16 October 2026. CVE-2026-102551 allows remote attackers to manipulate IPv6 gateway and routing configuration via spoofed Router Advertisements; the vulnerability is reachable in default configuration where ipconfigUSE_IPv6 and ipconfigUSE_RA are both enabled. CVE-2026-102552 allows remote attackers to poison the DNS cache by injecting replies from sources other than the queried server.
WHY IT MATTERSBoth vulnerabilities enable traffic interception and redirection on embedded and IoT devices running FreeRTOS-Plus-TCP. The IPv6 issue is exploitable in default configuration without requiring local network access. Devices using this stack for AWS IoT connectivity or edge services are exposed to man-in-the-middle attacks that can redirect traffic to attacker-controlled infrastructure.
WHAT TO DOInventory embedded and IoT devices running FreeRTOS-Plus-TCP V4.4.1 or earlier. Upgrade them to V4.4.2 and enable ipconfigDNS_CHECK_REPLY_SOURCE_IP in FreeRTOSIPConfig.h: source-IP checking is disabled by default, so upgrading alone does not fix CVE-2026-102552. If you cannot upgrade immediately, setting ipconfigUSE_RA to 0 is a workaround for CVE-2026-102551 only; it does not address CVE-2026-102552. See AWS Security Bulletin 2026-139-AWS for the current guidance.
Original text (as first published, superseded)
WHAT TO DOInventory all embedded and IoT devices running FreeRTOS-Plus-TCP to identify those on V4.4.1 or earlier. Check AWS Security Bulletin 2026-139-AWS for patch availability and apply updates to affected devices. If immediate patching is not feasible, disable IPv6 RA processing by setting ipconfigUSE_RA to 0 as a temporary mitigation for CVE-2026-102551.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP
+https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/
+Fri, 16 Oct 2026 17:34:49 +0000
+
+Bulletin ID: 2026-139-AWS
+
+Scope: AWS
+
+Content Type: Important (requires attention)
+
+Publication Date: 10/16/2026 10:15 AM PDT
+Description:
+FreeRTOS-Plus-TCP is an open-source, thread-safe TCP/IP stack for the FreeRTOS kernel, distributed by Amazon for use on embedded and IoT devices. AWS identified two issues with FreeRTOS-Plus-TCP, affecting multiple versions.
+CVE-2026-102551: improper verification of the source of a communication channel in the IPv6 Router Advertisement handler. The handler does not fully validate that a received Router Advertisement originates from an on-link source before acting on it. Under certain conditions, a remote third-party might influence an endpoint's IPv6 gateway, prefix, and address configuration, potentially enabling interception of the device's IPv6 traffic. This issue is reachable in the library's default configuration, where ipconfigUSE_IPv6 and ipconfigUSE_RA are both enabled.
+CVE-2026-102552: improper verification of the source of a communication channel in the DNS resolver. The resolver does not fully validate that a DNS reply originates from the server that was queried before accepting it. Under certain conditions, a remote third-party might insert a chosen address into the device's DNS cache, potentially redirecting the device's subsequent connections for the affected name.
+Impacted versions:
+- CVE-2026-102551 (Router Advertisement): <= V4.4.1
+
+- CVE-2026-102552 (DNS resolver): <= V4.4.1
+Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.55
triage reasoningAWS-distributed TCP/IP stack with remote exploitation paths affecting embedded systems in cloud infrastructure.
signalsknown AWS security bulletin with CVE identifiers · affects AWS-distributed open-source library (FreeRTOS-Plus-TCP) · remote exploitation vectors (IPv6 RA spoofing, DNS cache poisoning) · affects embedded/IoT devices running AWS infrastructure or edge services · impacted versions clearly specified (<=V4.4.1) · default configuration vulnerable
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)