Quick answers
- Is CVE-2026-14607 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14607 being exploited in the wild.
- How severe is CVE-2026-14607?
- Medium severity, with a CVSS score of 5.5, published 3 July 2026.
- Which products and versions are affected?
- RT-Thread up to 5.0.2.
- Is there a fix for CVE-2026-14607?
- A patch was published on 2026-06-09: Pull request to fix the issue submitted on GitHub Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14607 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-14607?
- Check whether you run RT-Thread at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A memory corruption vulnerability (CWE-119) exists in RT-Thread up to version 5.0.2 within the 'sys_getaddrinfo' system call located in 'components/lwp/lwp_syscall.c'. The issue stems from the kernel trusting a nested user-provided pointer ('ai_addr') without adequate validation. In builds using the Memory Management Unit (MMU), the kernel dereferences this nested pointer and performs writes in kernel context, allowing a local process to redirect kernel writes to memory locations outside of the validated user space. An attacker with local access can exploit this to cause memory corruption and system instability. A pull request (#11454) has been submitted to harden pointer handling by copying user inputs to kernel temporaries and validating nested destinations before writeback.
Affected products
- RT-Thread RT-Thread up to 5.0.2
Timeline
- 2026-06-09: patched: Pull request to fix the issue submitted on GitHub
- 2026-07-03: advisory: NVD and VulDB published the vulnerability details