# CVE-2025-13406: Scanning for higher HART revision device leads into NULL pointer dereference in live list

> An attacker can cause a denial of service in Softing smartLink SW-HT by triggering a NULL pointer dereference during device scanning.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/AU:Y/R:A/RE:L/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-94m9-vhc7-hv4q

## What is CVE-2025-13406?

CVE-2025-13406 is a medium-severity vulnerability in Softing smartLink SW-HT, published on 17 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

NULL Pointer Dereference vulnerability in Softing Industrial Automation GmbH smartLink SW-HT (Webserver modules) allows HTTP DoS.This issue affects smartLink SW-HT: 1.43.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2025-13406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13406 is a medium-severity vulnerability in Softing smartLink SW-HT, published on 17 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13406 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-13406/ (Markdown: https://insights.sbomify.com/CVE-2025-13406/index.md)
```

## Sources

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

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