NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-13406

MEDIUM · 6.8 CVSS v4.0 Published 2026-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A NULL pointer dereference vulnerability in the webserver modules of Softing Industrial Automation GmbH smartLink SW-HT version 1.43 allows remote attackers to cause a denial of service via crafted HTTP requests. The vulnerability stems from improper memory handling when processing certain HTTP requests, leading to a crash when the application attempts to access a NULL pointer.

MitigationApply the vendor-provided security patch or firmware update for smartLink SW-HT version 1.43. If no patch is available, implement network segmentation and HTTP request rate limiting at the perimeter to reduce exploitability while awaiting an official fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
Y
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:A/V:X/RE:L/U:Red

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if smartLink SW-HT is installed
    Locate the smartLink SW-HT software on the system. This is typically found in the installation directory of Softing Industrial products or can be identified via system inventory tools. Check for directories named 'smartLink' or 'SW-HT' in program files.
    Affected if The software is present on the system
  2. Check the installed version number
    Access the smartLink SW-HT interface or check the software properties/installation details to determine the exact version. Typically found in the web UI footer, 'About' section, or Windows program properties. Compare against version 1.43.
    Affected if The installed version is exactly 1.43
  3. Verify the webserver module is enabled
    Access the smartLink SW-HT web interface via browser on the default HTTP port (typically port 80 or 443). If a web login page or status page loads, the webserver module is active.
    Affected if The webserver module is accessible and responding to HTTP requests
  4. Confirm network exposure of the web interface
    Check network configuration to determine if the smartLink SW-HT webserver is exposed to untrusted networks. Use 'netstat' or similar tools to identify listening ports and verify firewall rules allowing HTTP access.
    Affected if The webserver is reachable from network segments that contain untrusted or external hosts

A system is affected if smartLink SW-HT version 1.43 is installed with its webserver module enabled and accessible, as the NULL pointer dereference occurs when processing certain crafted HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patch or firmware update for smartLink SW-HT version 1.43. If no patch is available, implement network segmentation and HTTP request rate limiting at the perimeter to reduce exploitability while awaiting an official fix.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13406 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data