dbcve.org
Improper LockingWeakness · CWE-667

CVE-2025-10151

HIGH · 7.2 CVSS v4.0 Published 2025-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
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

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

Improper locking vulnerability in Softing Industrial Automation GmbH smartLink HW-PN and HW-DP gateways allows infected memory and/or resource leak exposure. The improper synchronization enables memory corruption or resource exhaustion, potentially exposing sensitive data or causing denial-of-service conditions.

MitigationUpdate affected gateways to patched firmware versions when available. Prioritize network segmentation and monitor for unusual resource consumption patterns as interim controls.

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

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/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:U/V:X/RE:M/U:Amber

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 gateway model
    Locate the physical device or check network inventory for Softing smartLink HW-PN or HW-DP gateway. Verify the model number on the device label or in the management interface.
    Affected if The device is a Softing smartLink HW-PN or HW-DP gateway
  2. Retrieve the installed firmware version
    Access the gateway web interface (typically via HTTP/HTTPS on the management IP) and navigate to System > Information or firmware settings to view the firmware version. Alternatively, use SNMP or the device CLI if available.
    Affected if The firmware version cannot be confirmed or is older than the patched version when released
  3. Verify the gateway is in active operation
    Check the gateway status page to confirm it is running and processing PROFINET (PN) or PROFIBUS (DP) traffic. Look for active connection counters or traffic statistics.
    Affected if The gateway shows active network interfaces and is processing industrial protocol traffic, exposing the locking mechanism to potential exploitation
  4. Check for abnormal resource consumption
    If accessible via the management interface, review system statistics for unusually high memory usage, CPU load, or network buffer counts that may indicate the vulnerability is being triggered.
    Affected if Memory usage is abnormally high or steadily increasing without corresponding workload

You are affected if you have a Softing smartLink HW-PN or HW-DP gateway running firmware that has not been updated to the patched version, and the device is actively processing industrial network traffic.

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

Update affected gateways to patched firmware versions when available. Prioritize network segmentation and monitor for unusual resource consumption patterns as interim controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10151 — 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-10151 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