Cyber Resilience

CVE-2025-10150

Published
28 October 2025
Modified
15 April 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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
EPSS Score 0.0024 16th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-10150 is a high-severity Deadlock (CWE-833) vulnerability in Softing Industrial Automation (inferred from references). Its CVSS base score is 8.7 (High).

Operationally, ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Webserver crash caused by scanning on TCP port 80 in Softing Industrial Automation GmbH gateways and switch.This issue affects smartLink HW-PN: from 1.02 through 1.03 smartLink HW-DP: 1.31

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-36010Shared CWE-833
CVE-2026-70616Shared CWE-833
CVE-2025-21313Shared CWE-833
CVE-2025-1713Shared CWE-833
CVE-2024-47506Shared CWE-833
CVE-2025-8312Shared CWE-833
CVE-2024-8447Shared CWE-833
CVE-2026-33904Shared CWE-833
CVE-2023-31084Shared CWE-833
CVE-2025-59463Shared CWE-833

Affected Assets

Softing
Industrial Automation
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

none

Change management may catch deadlock-related defects during reviews but does not directly address concurrency design.

References