# CVE-2026-102715: Memory corruption in eclipse-threadx/netxduo

> A heap buffer overflow in the mDNS responder allows remote attackers to corrupt memory or execute code via crafted network packets.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-2gf7-5224-5vrj, GHSA-rp9p-ggxc-p9xm

## What is CVE-2026-102715?

CVE-2026-102715 is a high-severity memory corruption vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Any host on the LAN can send two mDNS records and make the responder write past the end of its

transmit packet.

The string table stores each name in a slot rounded up to a multiple of four:

```c

/* addons/mdns/nxd_mdns.c:11436, 11443, 11447 */

memory_len = ((memory_len & 0xFFFFFFFC) + 8) & 0xFFFFFFFF;

...

len = *((USHORT*)(p - 2));           /* slot size, not string length */

if ((len == memory_len) && ... _nx_mdns_name_match(start, memory_ptr, memory_size) ...)

```

The lookup that decides whether an incoming name is already stored compares the rounded slot size,

so names of 12, 13, 14 and 15 characters share one bucket. A second name in the bucket is answered

with the pointer to the first, and the record then carries a string up to three bytes longer than

the length the caller accounted for. `_nx_mdns_packet_rr_add` (nxd_mdns.c:8911) sizes its only

bound check from that stale length, and `_nx_mdns_name_string_encode` writes the real string.

Two PTR records are enough, both ordinary mDNS responses to a `_http._tcp` query, with owner names

whose lengths fall in the same bucket:

```

==87491==ERROR: AddressSanitizer: heap-buffer-overflow

WRITE of size 1 at 0x611000000124 thread T5

    #0 _nx_mdns_name_string_encode  addons/mdns/nxd_mdns.c:13096
    #1 _nx_mdns_packet_rr_add       addons/mdns/nxd_mdns.c:8911

0x611000000124 is 0 bytes to the right of 228-byte region

```

The overflow is one to three bytes of attacker-influenced name data past `nx_packet_data_end`. In a

normal pool that lands in the next packet in the same pool rather than in a redzone, so the visible

effect is a corrupted neighbouring packet or a corrupted pool free list rather than a clean crash.

Compare the slot size against the stored string length before declaring a match, or keep the

string length in the slot header and return it to the caller so the encoder and the bound check

agree.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-102715?


## How do I fix CVE-2026-102715?

No fix has been published for CVE-2026-102715 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102715 being exploited?

There is no known exploitation of CVE-2026-102715 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102715 and fix it if it is affected.

What it is: CVE-2026-102715 is a high-severity memory corruption vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102715 in the wild and no public exploit code.

Affected product: eclipse-threadx/netxduo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102715/ (Markdown: https://insights.sbomify.com/CVE-2026-102715/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102715
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102715
- OSV: https://osv.dev/vulnerability/CVE-2026-102715

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102715/
Summaries are generated and may contain mistakes; the official description above is the record.