# CVE-2026-93003: NetX Duo Web HTTP server interprets request body content as HTTP header fields


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-qjvr-68c3-5qhg

## What is CVE-2026-93003?

CVE-2026-93003 is a medium-severity vulnerability in Eclipse ThreadX - NetX Duo, published on 20 Oct 2026. 

### Official description

The Web add-on's HTTP server searches the entire request packet for header fields instead of stopping at the end of the header section. A header field name placed in the request body is therefore reported to the server as though it were a header, which lets a client control request framing decisions it should not be able to reach.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

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

## Is CVE-2026-93003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93003 is a medium-severity vulnerability in Eclipse ThreadX - NetX Duo, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93003 in the wild and no public exploit code.

Affected product: Eclipse ThreadX - NetX Duo. 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-93003/ (Markdown: https://insights.sbomify.com/CVE-2026-93003/index.md)
```

## Sources

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

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