dbcve.org
NiagaraApplication · Tridium

CVE-2025-3944

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on QNX, Tridium Niagara Enterprise Security on QNX allows File Manipulation. This issue affects Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security: 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical permission assignment vulnerability in Tridium Niagara Framework and Niagara Enterprise Security on QNX allows unauthorized file manipulation due to incorrectly assigned permissions on critical resources. The vulnerability has a CVSS score of 9.8 and affects multiple version branches before 4.14.2, 4.15.1, and 4.10.11.

MitigationUpgrade Niagara Framework and Enterprise Security to versions 4.14.2u2, 4.15.u1, or 4.10u.11 as recommended by Tridium to address the permission assignment vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NiagaraApplication
Affected:= 4.10u10= 4.14u1= 4.15
Niagara Enterprise SecurityApplication
Affected:= 4.10u10= 4.14u1= 4.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Tridium Niagara is installed
    Locate Niagara installation directories or check for Niagara services running on the system. Look for common installation paths like C:/Niagara or /opt/niagara, and check for running niagara.exe or similar processes.
    Affected if Tridium Niagara Framework or Niagara Enterprise Security is found on the system
  2. Determine the installed Niagara version
    Access the Niagara About page in the Workbench UI, check the version.properties or version.txt file in the installation directory, or review startup logs for version information.
    Affected if The version is 4.10u10 or earlier, 4.14u1 or earlier, or 4.15 (any 4.15.x version before 4.15.1)
  3. Verify the operating system is QNX
    Check the host operating system using commands like 'uname -a', 'systeminfo', or by inspecting system properties. The vulnerability specifically affects the QNX platform implementation.
    Affected if The Niagara Framework is running on a QNX operating system
  4. Inspect file permissions on critical system resources
    Examine permission settings on Niagara configuration directories, lib folders, and system files. Look for overly permissive access controls that may allow unauthorized file manipulation.
    Affected if Critical directories or files have permissions that allow modification by unauthorized users or processes

The system is affected if it runs Tridium Niagara Framework or Niagara Enterprise Security on QNX with version 4.10u10 or earlier, 4.14u1 or earlier, or any 4.15.x version below 4.15.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Niagara Framework and Enterprise Security to versions 4.14.2u2, 4.15.u1, or 4.10u.11 as recommended by Tridium to address the permission assignment vulnerability.

Recommended fix High confidence

4.14.2u2 (for 4.14.x line) or 4.15u1 (for 4.15.x line) or 4.10u11 (for 4.10.x line)

  1. 1. Identify the currently installed Niagara Framework or Niagara Enterprise Security version using the system's about or version information panel.
  2. 2. Based on your current major version line, plan the upgrade path: if on 4.10.x, upgrade to 4.10u11; if on 4.14.x, upgrade to 4.14.2u2; if on 4.15.x, upgrade to 4.15u1.
  3. 3. Download the appropriate fixed version installer from the official Tridium/Honeywell support portal or Niagara Community documentation.
  4. 4. Review upgrade documentation for any prerequisites or migration considerations specific to your deployment.
  5. 5. Create a complete backup of the Niagara station, including all configuration files, databases, and custom modules.
  6. 6. Test the upgrade in a non-production environment first to verify compatibility with existing custom modules and integrations.
  7. 7. Schedule a maintenance window and perform the upgrade following the official installation guide.
  8. 8. After upgrade, verify that the file permission vulnerability is resolved by confirming proper permission assignments on critical system files.
Caveat Upgrading between major versions may require module compatibility verification; custom modules written for older versions may need recompilation or updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Niagara Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3944 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data