dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-10685

HIGH · 7.7 CVSS v4.0 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
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

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 · high confidence

Heap-based buffer overflow vulnerability in the webserver modules of Softing Industrial Automation smartLink SW-PN (through v1.03) and smartLink SW-HT (through v1.42) allows overflow of heap-allocated buffers, potentially enabling remote code execution or denial of service.

MitigationApply vendor-supplied firmware patches when available; until then, isolate affected devices behind firewalls or network segmentation to reduce attack surface.

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
None
Authentication
Y
User interaction
None
Scope
X

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/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 the smartLink device model
    Access the device web interface or check the device label/datasheet to determine if it is a smartLink SW-PN or smartLink SW-HT variant
    Affected if Device model is smartLink SW-PN or smartLink SW-HT
  2. Check the installed firmware version
    Log into the device web interface and navigate to the System Information or Firmware Update page to view the current firmware version. Alternatively, use the device's management interface or consult vendor documentation for CLI commands to retrieve the firmware version
    Affected if Firmware version is 1.03 or lower for SW-PN, or 1.42 or lower for SW-HT
  3. Confirm the webserver module is enabled
    Access the device configuration settings and verify if the embedded webserver (HTTP/HTTPS service) is enabled. This is typically found under Network Settings, Services, or Web Server configuration sections in the device management interface
    Affected if Webserver module is currently enabled and running
  4. Assess network exposure of the device
    Review network configuration to determine if the device webserver is accessible from untrusted networks. Check firewall rules, VLAN assignments, and whether the device is directly exposed to the internet or only accessible from isolated industrial network segments
    Affected if Device webserver is reachable from network segments outside the trusted industrial zone

A user is affected if the device is a smartLink SW-PN (firmware <=1.03) or SW-HT (firmware <=1.42) with the webserver module enabled and accessible from a network where the vulnerability could be exploited.

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 vendor-supplied firmware patches when available; until then, isolate affected devices behind firewalls or network segmentation to reduce attack surface.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-10685 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