# CVE-2025-10151: Malicious TCP/IP thread locking leads into diverse malfunctions

> Improper locking in Softing industrial gateways allows attackers to cause malfunctions and expose memory or resources via malicious TCP/IP traffic.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L/AU:Y/R:U/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-3hj7-rw79-jh5m

## What is CVE-2025-10151?

CVE-2025-10151 is a high-severity vulnerability in Softing Industrial Automation GmbH smartLink HW-DP, published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper locking vulnerability in Softing Industrial Automation GmbH gateways allows infected memory and/or resource leak exposure.This issue affects

smartLink HW-PN: from 1.02 through 1.03

smartLink HW-DP: 1.31

Weakness: CWE-667 (Improper Locking)

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


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

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

## Is CVE-2025-10151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10151 is a high-severity vulnerability in Softing Industrial Automation GmbH smartLink HW-DP, published on 28 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10151 in the wild and no public exploit code.

Affected product: Softing Industrial Automation GmbH smartLink HW-DP. 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-10151/ (Markdown: https://insights.sbomify.com/CVE-2025-10151/index.md)
```

## Sources

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

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