dbcve.org
NiagaraApplication · Tridium

CVE-2025-3940

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 Use of Validation Framework vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Input Data 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 · high confidence

An Improper Use of Validation Framework vulnerability in Tridium Niagara Framework allows attackers to manipulate input data due to improper validation handling. This affects both the standard Niagara Framework and Niagara Enterprise Security on Windows, Linux, and QNX platforms across multiple version branches.

MitigationUpgrade Niagara Framework and Niagara Enterprise Security to vendor-recommended versions (4.14.2u2, 4.15.u1, or 4.10u.11) to address the validation framework misuse. Prioritize critical systems given the CVSS 9.8 severity.

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. Locate Niagara Framework installation directory
    On Windows, check C:\Niagara\ or the custom install path; on Linux/QNX, check /opt/niagara/ or the configured installation directory. Look for the 'niagara' folder containing the framework runtime.
    Affected if The Niagara Framework is installed on the system.
  2. Identify Niagara version
    Open the 'version.txt' or 'about.properties' file in the Niagara home directory. Alternatively, access the Niagara Station via web browser (port 80/8080) and navigate to About > System Information to view the exact version and build number.
    Affected if Version reads exactly 4.10u10, 4.14u1, or 4.15 (without u1 update).
  3. Confirm if Niagara Enterprise Security is installed
    Check for the presence of an 'enterprise' or 'security' module folder within the Niagara modules directory (niagara/home/modules). The Enterprise Security variant is typically installed as a separate module package.
    Affected if Niagara Enterprise Security module is present and version matches 4.10u10, 4.14u1, or 4.15.
  4. Check platform operating system
    Identify the host OS by running 'systeminfo' on Windows, 'uname -a' on Linux, or checking system properties. The vulnerability affects Windows, Linux, and QNX platforms.
    Affected if Running Windows, Linux, or QNX with an affected Niagara version.
  5. Compare against fixed version branch
    If version is 4.10.x, confirm build is below 4.10u11. If 4.14.x, confirm build is below 4.14u2. If 4.15.x, confirm build is below 4.15u1. Versions 4.14.2u2, 4.15.u1, and 4.10u.11 are the minimum fixed releases.
    Affected if Installed version is any 4.10u10, 4.14u1, or 4.15 release without subsequent updates.

A system is affected if it runs Tridium Niagara or Niagara Enterprise Security versions 4.10u10, 4.14u1, or 4.15 on Windows, Linux, or QNX platforms, as these versions contain the improper validation handling vulnerability.

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 Niagara Enterprise Security to vendor-recommended versions (4.14.2u2, 4.15.u1, or 4.10u.11) to address the validation framework misuse. Prioritize critical systems given the CVSS 9.8 severity.

Recommended fix High confidence

Niagara Framework/Enterprise Security 4.10u11, 4.14.2, or 4.15.1 (or newer: 4.14.2u2, 4.15u1)

  1. 1. Identify the current installed version of Niagara Framework or Niagara Enterprise Security
  2. 2. Download the appropriate fixed version from the official Tridium/Honeywell distribution channel
  3. 3. Schedule a maintenance window as upgrades may require system restart
  4. 4. Back up the Niagara station and configuration files before proceeding
  5. 5. Follow Tridium's standard upgrade procedure for your platform (Windows, Linux, or QNX)
  6. 6. Upgrade to one of the fixed versions: 4.10u11, 4.14.2, or 4.15.1 (or newer patched variants 4.14.2u2, 4.15u1 as recommended by vendor)
  7. 7. Verify the upgrade completed successfully and all services are running
  8. 8. Test critical functionality to ensure normal operations
Caveat Standard Niagara upgrade considerations apply - review release notes for breaking changes between your current version and target version; test in non-production environment first

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

Fix this in Niagara Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3940 — 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-3940 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