--- id: "GHSA-pjq5-fqrr-g6pv" kind: "vulnerability" aliases: ["GHSA-pjq5-fqrr-g6pv"] title: "CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP" severity: "unknown" cvss: null epss: null exploited: false status: "open" category: "package" products: [] ecosystems: [] tags: ["aws", "dns", "embedded", "firmware", "freertos", "iot", "ipv6", "lab-disclosure", "package"] not_affected_if: ["dns-source-check-enabled", "ipv6-disabled", "ra-disabled", "version-4.4.2-or-later"] published_at: "2026-10-16T00:00:00+00:00" first_seen_at: "2026-10-24T18:56:55+00:00" updated_at: "2026-10-25T05:27:50+00:00" sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/", "first_seen_at": "2026-10-24T18:56:55+00:00"}] --- # CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP FreeRTOS-Plus-TCP up to V4.4.1 accepts IPv6 Router Advertisements and DNS replies without properly checking their source, so a remote third party can change a device's IPv6 gateway and prefix or insert a chosen address into its DNS cache. An attacker could use this to intercept IPv6 traffic or redirect the device's later connections to hosts they control. _Summary, check and fix written by a model from the sources; labelled as such._ ## How to check - Check the FreeRTOS-Plus-TCP version in the firmware or vendored source, for example by reading the version header or `FreeRTOS_IPv6.h` and `FreeRTOS_DNS.c` in the imported code. - Check `FreeRTOSIPConfig.h` for `ipconfigUSE_IPv6` and `ipconfigUSE_RA` set to `ipconfigENABLE`, which is the default configuration that is affected. - Check `FreeRTOSIPConfig.h` for `ipconfigDNS_CHECK_REPLY_SOURCE_IP`; if it is absent or not enabled, the DNS fix is not active. ## Fix - Upgrade FreeRTOS-Plus-TCP to `V4.4.2` or later, and patch any forked or derivative copies of the code. - Enable `ipconfigDNS_CHECK_REPLY_SOURCE_IP` in `FreeRTOSIPConfig.h` after upgrading, since the DNS fix is opt-in and disabled by default. - If upgrading is not immediately possible, set `ipconfigUSE_RA` to `ipconfigDISABLE` (or disable IPv6 with `ipconfigUSE_IPv6 = ipconfigDISABLE`) where IPv6 autoconfiguration is not needed. - Deploy RA Guard and/or SEND on the local link; this covers only the on-link vector. ## Timeline - 2026-10-24T18:56:55+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/ — AWS: CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP ## Documents - [advisory] AWS: CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP https://aws.amazon.com/security/security-bulletins/rss/2026-139-aws/ ## From the sources CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP ### CVE-2026-102551 & CVE-2026-102552 - Issue with FreeRTOS-Plus-TCP 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 Resolution: This issue has been addressed in FreeRTOS-Plus-TCP version V4.4.2. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. For the DNS resolver issue, responder source-IP validation is provided as an opt-in option and is disabled by default; upgrading alone does not remediate it. To remediate, upgrade to V4.4.2 and enable ipconfigDNS_CHECK_REPLY_SOURCE_IP in FreeRTOSIPConfig.h. Workarounds: - CVE-2026-102551 (Router Advertisement): If upgrading is not immediately possible, disable IPv6 Router Advertisement processing by setting ipconfigUSE_RA to ipconfigDISABLE (or disable IPv6 entirely with ipconfigUSE_IPv6 = ipconfigDISABLE) in FreeRTOSIPConfig.h where the device does not require IPv6 RA-based autoconfiguration. On the network side, deploying RA Guard and/or SEND on the local link mitigates the on-link vector but does not address the off-link vector reachable during lease-renewal windows. - CVE-2026-102552 (DNS resolver): There is no configuration-only workaround on affected versions, because responder source-IP validation does not exist prior to V4.4.2. Where feasible, restricting the device to a trusted local resolver and protecting the local network path reduces unintended access to off-path reply forgery but does not eliminate the issue. References: - CVE-2026-102551 - CVE-2026-102552 - GHSA-pjq5-fqrr-g6pv - GHSA-h4fw-pv82-p7h5 Acknowledgement: We would like to thank Cipher / Causal Security for collaborating on this issue through the coordinated vulnerability disclosure process. Please email aws-security@amazon.com with any security questions or concerns. --- _Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_