dbcve.org
NiagaraApplication · Tridium

CVE-2025-3941

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 Handling of Windows ::DATA Alternate Data Stream vulnerability in Tridium Niagara Framework on Windows, Tridium Niagara Enterprise Security on Windows 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

The Tridium Niagara Framework on Windows improperly handles Windows Alternate Data Streams (ADS), specifically the ::DATA stream. This allows an attacker to manipulate input data through the ADS mechanism, potentially enabling injection or manipulation of data that the application processes. The vulnerability has a critical CVSS score of 9.8, indicating severe potential impact.

MitigationTridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11 to remediate this 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 the host operating system
    Verify if the Niagara deployment is running on Windows, since this vulnerability specifically affects Windows Alternate Data Streams. Run 'systeminfo' or check System Properties.
    Affected if The host OS is Windows (the vulnerability does not apply to non-Windows deployments)
  2. Determine the Niagara Framework version
    Locate the Niagara installation directory and check the version file or banner. Typically found in the 'conf' folder or via the niagara version command (nRJvm -version). Common paths: C:\Niagara\conf\version.properties or within the Niagara work directory.
    Affected if The installed version matches 4.10u10, 4.14u1, or 4.15 exactly or falls within these specific release lines
  3. Check Niagara Enterprise Security version if deployed
    If Niagara Enterprise Security is installed, identify its version through the same methods as the Framework version, typically within the Enterprise Security module directory or version info.
    Affected if Enterprise Security version matches 4.10u10, 4.14u1, or 4.15
  4. Verify ADS input processing is in use
    Review Niagara station configurations and any external data import mechanisms that could accept files from Windows sources. Inspect log files for any ADS-related operations or file handling that may process Windows-format input.
    Affected if The Niagara station processes external files or input data from Windows sources that could contain Alternate Data Streams

A system is affected if it runs on Windows with Niagara or Niagara Enterprise Security versions 4.10u10, 4.14u1, or 4.15 and processes external input files that could contain Windows Alternate Data Streams.

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

Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11 to remediate this vulnerability.

Recommended fix High confidence

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

  1. 1. Identify the currently installed Niagara Framework or Niagara Enterprise Security version by checking the system's About or version information.
  2. 2. Determine which version branch you are on (4.10.x, 4.14.x, or 4.15.x).
  3. 3. For Niagara Framework: Upgrade to version 4.10u11, 4.14.2u2, or 4.15u1 depending on your current branch.
  4. 4. For Niagara Enterprise Security: Upgrade to version 4.10u11, 4.14.2u2, or 4.15u1 depending on your current branch.
  5. 5. Before upgrading, review Tridium's upgrade documentation and ensure you have a complete backup of your system.
  6. 6. Test the upgrade in a non-production environment first to verify compatibility with your custom modules and integrations.
  7. 7. After upgrade, verify the vulnerability is resolved by checking the version information confirms the new fixed release is installed.
Caveat Review Tridium compatibility documentation before upgrading; custom modules may require updates for the new version; perform staging environment testing

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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