# CVE-2025-10685: HTTP POST with specific higher content length leads into heap corruption

> Heap-based buffer overflow in Softing smartLink webservers allows attackers to cause heap corruption via crafted HTTP POST requests.

- **Severity:** High 7.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:H/E:U/AU:Y/R:A/RE:L/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-9r22-hfr9-vvx7

## What is CVE-2025-10685?

CVE-2025-10685 is a high-severity memory corruption vulnerability in Softing smartLink SW-HT, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow vulnerability in Softing Industrial Automation GmbH smartLink SW-PN and smartLink SW-HT (Webserver modules) allows overflow buffers.This issue affects:

smartLink SW-PN: through 1.03

smartLink SW-HT: through 1.42

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-10685?


## How do I fix CVE-2025-10685?

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

## Is CVE-2025-10685 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10685 and fix it if it is affected.

What it is: CVE-2025-10685 is a high-severity memory corruption vulnerability in Softing smartLink SW-HT, published on 16 Mar 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-2025-10685 in the wild and no public exploit code.

Affected product: Softing smartLink SW-HT. 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-2025-10685/ (Markdown: https://insights.sbomify.com/CVE-2025-10685/index.md)
```

## Sources

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

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