# CVE-2026-102716: Denial of service in eclipse-threadx/netxduo

> Unauthenticated attackers can exhaust the RTSP server's packet pool via malformed Session headers, causing a denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-4637-2x4v-2wq5, GHSA-q462-246c-x3jc

## What is CVE-2026-102716?

CVE-2026-102716 is a high-severity denial of service vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated client can drain the RTSP server's packet pool with a couple of dozen requests

that carry a Session header the parser cannot convert.

The Session branch returns the raw NetX error code instead of an RTSP status code:

```c

/* addons/rtsp/nx_rtsp_server.c:2754 */

status = _nx_utility_string_to_uint(field_value_ptr, field_value_length, &session_id);

if (status)

{

    return(status);      /* NX_INVALID_PARAMETERS / NX_SIZE_ERROR / NX_OVERFLOW */

}

```

Every other branch of the same function maps its failure to an RTSP status first. The CSeq branch

eighteen lines earlier does exactly that (line 2736 returns NX_RTSP_STATUS_CODE_BAD_REQUEST). The

raw code then reaches `_nx_rtsp_server_error_response_send` (nx_rtsp_server.c:1234), which does not

recognise it, takes a path that returns without releasing the response packet it already allocated,

and the block never goes back to the pool.

Six requests with an empty Session header against a 22 packet pool:

```

valid requests:      after request 6: pool available = 21,  AFTER = 22 / 22

malformed requests:  after request 6: pool available = 16,  AFTER = 17 / 22

```

One block per request, not returned when the client disconnects. Twenty six requests take the pool

to zero and the server starts failing allocations, after which it serves nobody. If the pool is

shared with the rest of the application, as it is in the shipped sample, the rest of the stack

stops with it.

Convert the `_nx_utility_string_to_uint` failure in the Session branch into

NX_RTSP_STATUS_CODE_BAD_REQUEST the way the CSeq branch does, and release the response packet on

every exit path of `_nx_rtsp_server_error_response_send`.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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


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

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

## Is CVE-2026-102716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102716 is a high-severity denial of service vulnerability in eclipse-threadx/netxduo, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102716 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-102716/ (Markdown: https://insights.sbomify.com/CVE-2026-102716/index.md)
```

## Sources

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

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