# CVE-2026-85384: Authenticated Stack-Based Buffer Overflow in RE210 AC750 Configuration Import

> An authenticated attacker can trigger a stack-based buffer overflow via a crafted configuration file, leading to remote code execution on the device.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-j5wp-3x5f-9h6c

## What is CVE-2026-85384?

CVE-2026-85384 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. RE210 AC750, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in the httpd component of RE210 AC750 due to improper bounds checking in the splitString function when processing an uploaded configuration file. An authenticated attacker on the local network can upload a crafted configuration file to trigger the overflow, leading to remote code execution.

Successful exploitation may allow unauthorized access to sensitive information, modification of device configuration and network behavior, or disruption of device availability.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-85384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85384 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. RE210 AC750, published on 8 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-85384 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. RE210 AC750. 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-85384/ (Markdown: https://insights.sbomify.com/CVE-2026-85384/index.md)
```

## Sources

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

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