dbcve.org
NiagaraApplication · Tridium

CVE-2025-3945

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
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Tridium Niagara Framework on QNX, Tridium Niagara Enterprise Security on QNX allows Command Delimiters. 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 · high confidence

This is an argument injection vulnerability in the Tridium Niagara Framework and Niagara Enterprise Security running on QNX. The software fails to properly neutralize argument delimiters in commands, allowing an attacker to inject additional arguments that can be interpreted by the underlying system command processor. This can lead to arbitrary command execution with the privileges of the affected service.

MitigationUpgrade Tridium Niagara Framework and Niagara Enterprise Security to versions 4.14.2u2, 4.15.u1, or 4.10u.11 (or later) as recommended by the vendor.

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 the Niagara Framework version
    Locate the version number in the Niagara installation. In the Niagara web interface, go to the 'About' page or check the 'Version' information in the station administration. Alternatively, examine version.properties or similar version files in the Niagara installation directory.
    Affected if The installed version is exactly 4.10u10, 4.14u1, or 4.15
  2. Identify the Niagara Enterprise Security version
    If Enterprise Security module is installed, check its version through the Niagara modules administration page or the modules directory within the installation.
    Affected if The Enterprise Security module version is exactly 4.10u10, 4.14u1, or 4.15
  3. Verify the host operating system is QNX
    Determine the operating system on which the Niagara instance is running. Check system information through the Niagara station configuration, host machine diagnostics, or by consulting system documentation for the deployment environment.
    Affected if The Niagara Framework or Enterprise Security is running on a QNX-based operating system
  4. Identify modules or features that invoke system commands
    Review the Niagara station configuration for modules or station services that execute external system commands. Check module configurations, custom scripts, or any integration points that could accept user-supplied arguments to pass to OS-level commands.
    Affected if The deployment includes modules or features that execute system commands and could potentially accept injectable arguments

The environment is vulnerable if Niagara Framework or Enterprise Security version 4.10u10, 4.14u1, or 4.15 is installed on a QNX operating system with command execution capabilities accessible to users.

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 Tridium Niagara Framework and Niagara Enterprise Security to versions 4.14.2u2, 4.15.u1, or 4.10u.11 (or later) as recommended by the vendor.

Recommended fix High confidence

4.10u11 or 4.14.2u2 or 4.15u1 (depending on your release train)

  1. 1. Identify the currently installed Niagara Framework or Niagara Enterprise Security version
  2. 2. Determine which release train you are on (4.10.x, 4.14.x, or 4.15.x)
  3. 3. Download the appropriate fixed version from the official Tridium/Honeywell support portal
  4. 4. Review release notes for the target version (4.10u11, 4.14.2u2, or 4.15u1) for any migration requirements
  5. 5. Back up the current Niagara configuration and database
  6. 6. Perform the upgrade following the official Tridium upgrade documentation
  7. 7. Verify the installation and test critical functionality after upgrade
Caveat Review Tridium release notes for your specific version path for any configuration or compatibility considerations

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-3945 — 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-3945 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