CVE-2025-3945 is a high severity argument injection flaw (CVSS 7.2) in Tridium Niagara Framework and Enterprise Security on QNX. Releases before 4.14.2, 4.15.1 and 4.10.11 are affected. Tridium recommends 4.14.2u2, 4.15u1 or 4.10u11, so find your QNX based controllers and plan the update.
What's affected
The record names Tridium Niagara Framework and Niagara Enterprise Security on QNX. Affected versions are before 4.14.2, before 4.15.1 and before 4.10.11, so three supported release lines are covered. The description says the flaw allows command delimiters to be used, which is how the record describes argument injection.
Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15u1 or 4.10u11. The record writes the last two with slightly different punctuation, so confirm the exact build names in Tridium's bulletin.
The record lists the weakness as CWE-88 (argument injection). The CVSS 3.1 score is 7.2 (high), with the vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. The vector shows the flaw can be reached over the network, and a high privilege account is needed. Confidentiality impact is rated high, integrity high and availability high.
The record does not say this flaw is exploited in the wild, and the CISA Known Exploited Vulnerabilities flag is false.
How to check if you're exposed
Niagara is an industrial and building automation platform, so the checks are about inventory and version.
- Find the Niagara version on each system. Open the product's version or about information in Workbench, or in the station's platform details, and note the release line (4.10, 4.14 or 4.15) and the update level.
- Compare it with the fixed builds in the record: 4.14.2u2, 4.15u1 and 4.10u11. Anything older than the fixed build in its line needs the update.
- Check which Niagara controllers run QNX. This CVE names QNX only.
- Open the Tridium and Honeywell security notices listed in the record, and check the technical bulletin for this CVE for any extra steps.
Niagara is a vendor product, not a package you install from a registry, so a dependency scan will not show it. The Gold directory lets you look up other CVEs by product, and your asset inventory is the right place to track Niagara versions.
What to do now
- Plan the upgrade to the fixed build for your release line: 4.14.2u2, 4.15u1 or 4.10u11. Confirm the exact names in Tridium's bulletin.
- Take a backup of each station and its configuration before you upgrade, and test on a non production system if you have one.
- Keep Niagara systems off the public internet. Place them in a segmented network, reachable only through a VPN or a managed gateway.
- Review which accounts and services can reach the platform, and remove anything that is not needed.
- Inventory every Niagara system, including the operating system it runs on, so that you can tell which of the related CVEs apply to each.
- Subscribe to Tridium and Honeywell security notices so the next bulletin reaches you quickly.
Why it matters
The record lists CWE-88, improper neutralization of argument delimiters in a command. When a program builds a command line from input, extra text can add or change arguments. The program being called then does something the developer did not plan.
The vector requires a high privilege account and rates confidentiality, integrity and availability all as high, which gives the 7.2 score. The record does not say what the injected arguments can reach, so follow the vendor bulletin. As with other flaws that need a privileged account, protecting administrator credentials and limiting who can log in is a useful second layer.
Quick check
Which versions fix CVE-2025-3945?
The record says versions before 4.14.2, 4.15.1 and 4.10.11 are affected and recommends 4.14.2u2, 4.15u1 or 4.10u11. Confirm the names in Tridium's bulletin.
Is it a Windows issue?
No. This entry names QNX only.
Sources
- Gold entry for CVE-2025-3945
- NVD record for CVE-2025-3945, published 2025-05-22, as summarized above
- Honeywell product security notices, listed in the record
- Niagara Community technical bulletins, listed in the record
Last reviewed: 18 October 2026.