Safeguard
Vulnerability Analysis•

CVE-2025-3936: Medium Permissions Flaw in Tridium Niagara

CVE-2025-3936 is a medium incorrect permission assignment in Tridium Niagara on Windows before 4.14.2, 4.15.1 and 4.10.11. Upgrade to the fixed builds.

Safeguard Security Team
4 min read

CVE-2025-3936 is a medium severity incorrect permission assignment (CVSS 6.5) in Tridium Niagara Framework and Enterprise Security on Windows. Releases before 4.14.2, 4.15.1 and 4.10.11 are affected. Tridium recommends upgrading to 4.14.2u2, 4.15u1 or 4.10u11, so find your Windows hosts and plan the update.

What's affected

The record names Tridium Niagara Framework and Niagara Enterprise Security on Windows. 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 exploiting incorrectly configured access control security levels on Windows.

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-732 (incorrect permission assignment for a critical resource). The CVSS 3.1 score is 6.5 (medium), with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. The vector shows the flaw can be reached only from the local machine, and a low privilege account is needed. Confidentiality impact is rated high, integrity no and availability no.

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.

  1. 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.
  2. 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.
  3. Check which Niagara hosts run Windows. This CVE names Windows only.
  4. 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

  1. Review file and folder permissions on the Niagara installation directory on Windows hosts, and remove access for accounts that do not need it.
  2. 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.
  3. Take a backup of each station and its configuration before you upgrade, and test on a non production system if you have one.
  4. Keep Niagara systems off the public internet. Place them in a segmented network, reachable only through a VPN or a managed gateway.
  5. Review which accounts and services can reach the platform, and remove anything that is not needed.
  6. Inventory every Niagara system, including the operating system it runs on, so that you can tell which of the related CVEs apply to each.
  7. Subscribe to Tridium and Honeywell security notices so the next bulletin reaches you quickly.

Why it matters

The record describes incorrect permission assignment for a critical resource, listed as CWE-732. Permissions decide who can read, change or run something on a system. When a critical resource has looser permissions than it needs, a user with a limited account may reach it.

The vector rates this as a local flaw that needs a low privilege account, with a high impact on confidentiality, and a changed scope. That is why the score is 6.5 despite the narrow access. In a building or plant network, a local account on a Windows host is often easier to obtain than people expect, for example through shared engineering workstations. Treat the Windows hosts as the first to patch.

Quick check

Which versions fix CVE-2025-3936?

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.

Does it affect Linux or QNX?

This entry names Windows only. Other CVEs from the same disclosure cover other platforms, so check each one.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.