Tridium develops the Niagara platform and related automation frameworks, which serve as control systems and integration hubs for building automation, energy management, and industrial IoT environments—deployments where security patching cycles are often protracted and device lifespans extend well beyond vendor support windows. Vulnerabilities affecting this vendor skew strongly toward critical-severity outcomes and recur across its Niagara product line and Edge variants through weakness classes centered on path traversal, authentication bypass, improper credential handling, and insufficient access controls—flaws that can afford direct command execution or unauthorized system manipulation in operational technology settings. The vendor's vulnerability footprint is modest in absolute volume but carries outsized strategic weight because Niagara instances frequently sit at network perimeters and control points where exploitation can ripple across entire building or campus infrastructure. Defenders should prioritize inventorying Niagara deployments and applying vendor updates systematically, as the combination of critical severity and OT-deployment context elevates even isolated disclosures to high operational risk. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Tridium over time
Signals from CVEs in this vendor scope (20 CVEs).
20 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-16748CRITICAL An attacker can log into the local Niagara platform (Niagara AX Framework Versions 3.8 and prior or Niagara 4 Framework Versions 4.4 and prior) using a disabled account name and a | Aug 20, 2018 | 9.8 | 33 | NO | NO |
CVE-2012-4701HIGH Directory traversal vulnerability in Tridium Niagara AX 3.5, 3.6, and 3.7 allows remote attackers to read sensitive files, and consequently execute arbitrary code, by leveraging (1 | Feb 15, 2013 | 9.3 | 30 | NO | NO |
CVE-2025-3938CRITICAL Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Cryptanalysis. This | May 22, 2025 | 9.8 | 29 | NO | NO |
CVE-2025-3936CRITICAL Incorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on Windows, Tridium Niagara Enterprise Security on Windows allows Exploiting Incorr | May 22, 2025 | 9.8 | 29 | NO | NO |
CVE-2025-3945CRITICAL Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Tridium Niagara Framework on QNX, Tridium Niagara Enterprise Security on QNX all | May 22, 2025 | 9.8 | 27 | NO | NO |
CVE-2025-3944CRITICAL Incorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on QNX, Tridium Niagara Enterprise Security on QNX allows File Manipulation. This i | May 22, 2025 | 9.8 | 27 | NO | NO |
CVE-2025-3941CRITICAL Improper Handling of Windows ::DATA Alternate Data Stream vulnerability in Tridium Niagara Framework on Windows, Tridium Niagara Enterprise Security on Windows allows Input Data Ma | May 22, 2025 | 9.8 | 27 | NO | NO |
CVE-2025-3937CRITICAL Use of Password Hash With Insufficient Computational Effort vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux | May 22, 2025 | 9.8 | 27 | NO | NO |
CVE-2017-16744HIGH A path traversal vulnerability in Tridium Niagara AX Versions 3.8 and prior and Niagara 4 systems Versions 4.4 and prior installed on Microsoft Windows Systems can be exploited by | Aug 20, 2018 | 7.2 | 27 | NO | NO |
CVE-2025-3940CRITICAL 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 | May 22, 2025 | 9.8 | 25 | NO | NO |
Signals from CVEs in this vendor scope (20 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Tridium.
Media articles that mention a CVE ID that affects a product developed by Tridium — matched by CVE ID, not by vendor name.