Cyber Resilience

CVE-2025-3450

Published
07 October 2025
Modified
15 April 2026
CVSS Score v4 9.3
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:H/VA:H/SC:N/SI:H/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:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0026 18th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-3450 is a critical-severity Improper Resource Locking (CWE-413) vulnerability. Its CVSS base score is 9.3 (Critical).

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

EU & UK References

Vulnerability Data

An Improper Resource Locking vulnerability in the SDM component of B&R Automation Runtime versions before 6.3 and before Q4.93 may allow an unauthenticated network-based attacker to delete data causing denial of service conditions.

CWE(s)
CWE-413

Related Threats

CVEs Like This One

CVE-2023-32253Shared CWE-413
CVE-2026-44608Shared CWE-413
CVE-2023-28649Shared CWE-413
CVE-2023-2269Shared CWE-413
CVE-2023-2430Shared CWE-413
CVE-2025-69198Shared CWE-413
CVE-2023-33951Shared CWE-413
CVE-2026-32748Shared CWE-413

Affected Assets

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

Mitigating Controls

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 mostly match
prevents

Secure SDLC practices (reviews, static analysis, coding standards) directly prevent improper locking defects from being introduced.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect locking defects but does not itself implement locking controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires proper resource management patterns that prevent improper locking.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate exclusive-access controls and locking mechanisms.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency and resource-locking design rules.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit missing or incorrect resource locks.

References