To mitigate this issue, users should upgrade to the fixed version when available.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 04 May 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:amazon:freertos-plus-tcp:*:*:*:*:*:*:*:* |
Thu, 30 Apr 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Amazon
Amazon freertos-plus-tcp |
|
| Vendors & Products |
Amazon
Amazon freertos-plus-tcp |
Wed, 29 Apr 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 29 Apr 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 29 Apr 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Insufficient validation of the prefix length field in IPv6 Router Advertisement processing in FreeRTOS-Plus-TCP before V4.2.6 and V4.4.1 allows an adjacent network actor to cause memory corruption by sending a crafted Router Advertisement with a prefix length value exceeding the maximum valid length, resulting in a heap buffer overflow. Users processing IPv4 RA only are not impacted. To mitigate this issue, users should upgrade to the fixed version when available. | |
| Title | Out-of-Bounds Write via Unsanitized Prefix Length in Router Advertisement Processing in FreeRTOS-Plus-TCP | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: AMZN
Published:
Updated: 2026-04-29T22:14:34.199Z
Reserved: 2026-04-29T14:27:53.201Z
Link: CVE-2026-7426
Updated: 2026-04-29T19:33:08.227Z
Status : Analyzed
Published: 2026-04-29T20:16:32.143
Modified: 2026-05-04T13:12:17.510
Link: CVE-2026-7426
No data.
OpenCVE Enrichment
Updated: 2026-04-30T08:15:31Z