Cyber Resilience

CVE-2025-3940

Tridium Niagara 4.10u10 … 4.15

Published
22 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0032 24th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-3940 is a medium-severity Improper Use of Validation Framework (CWE-1173) vulnerability in Tridium Niagara. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 24th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Improper Use of Validation Framework vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Input Data Manipulation. This issue affects Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security:…

more

before 4.14.2, before 4.15.1, before 4.10.11. Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-3942Same product: Blackberry Qnx
CVE-2025-3939Same product: Blackberry Qnx
CVE-2025-3943Same product: Blackberry Qnx
CVE-2025-3938Same product: Blackberry Qnx
CVE-2025-3944Same product: Blackberry Qnx
CVE-2025-3937Same product: Blackberry Qnx
CVE-2025-3945Same product: Blackberry Qnx
CVE-2022-47986Same product: Linux Linux Kernel
CVE-2026-33674Shared CWE-1173
CVE-2024-58360Shared CWE-1173

Affected Assets

tridium
niagara
4.10u10, 4.14u1, 4.15
tridium
niagara enterprise security
4.10u10, 4.14u1, 4.15

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)
  • V2.2.2
  • V1.3.1
  • V1.4.2
  • V15.3.7

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incorrect or missing use of supplied validation frameworks during development.

SI-10 directly requires checking validity of inputs, which structurally prevents failure to use or misuse of a validation framework.

Requiring documented development processes and tools can mandate correct adoption of language or library validation frameworks.

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 directly require correct adoption of language-provided or library input-validation frameworks.

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 can detect missing validation but does not enforce framework adoption.

prevents

Secure development life cycle mandates use of approved validation frameworks and libraries.

prevents

Application security requirements explicitly call for proper input validation mechanisms.

prevents

Secure architecture principles encourage validated input handling but do not prescribe frameworks.

prevents

Secure coding directly requires correct use of language-provided or approved validation libraries.

References