dbcve.org
NiagaraApplication · Tridium

CVE-2025-3938

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
Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Cryptanalysis. 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

A Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, and QNX allows cryptanalysis due to a flaw in the cryptographic implementation. This weakness could enable attackers to compromise encrypted data by exploiting the missing step in the encryption/decryption process.

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

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 Framework is installed
    Check for Niagara installation directories or running Niagara services on the system. On Windows, look in typical installation paths like C:\Niagara or check for Niagara services. On Linux/QNX, check directories like /opt/niagara or /usr/niagara.
    Affected if Niagara Framework is present on the system
  2. Determine the installed Niagara version
    Locate the version information file or use platform-specific commands. Common methods include checking a version file in the installation directory, inspecting the niagara.version property, or querying the Niagara service via command line if accessible.
    Affected if The installed version matches 4.10u10, 4.14u1, or 4.15
  3. Check if Niagara Enterprise Security is installed
    Identify if the Niagara Enterprise Security module/component is present. This may be listed in the Niagara installation, or as a separate product installation.
    Affected if Niagara Enterprise Security version 4.10u10, 4.14u1, or 4.15 is installed
  4. Verify the operating system platform
    Confirm the host operating system is Windows, Linux, or QNX, as these are the affected platforms listed for this vulnerability.
    Affected if Running on Windows, Linux, or QNX with a vulnerable Niagara version installed
  5. Identify if cryptographic features are in use
    Review Niagara station configuration files for encryption settings, password storage mechanisms, or security module configurations that utilize the affected cryptographic implementation.
    Affected if The system uses Niagara's built-in encryption for sensitive data storage or communication

A system is affected if it runs Tridium Niagara Framework or Niagara Enterprise Security version 4.10u10, 4.14u1, or 4.15 on Windows, Linux, or QNX, particularly if cryptographic features are enabled for data protection.

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 versions 4.14.2u2, 4.15.u1, or 4.10u.11 as recommended by Tridium.

Recommended fix High confidence

Upgrade to Niagara Framework/Niagara Enterprise Security 4.10u11, 4.14.2u2, or 4.15u1 (depending on your current version branch)

  1. 1. Identify the current Niagara Framework or Niagara Enterprise Security version by checking the system diagnostics or About section
  2. 2. Review the current version against the affected versions: 4.10u10, 4.14u1, and 4.15
  3. 3. Determine the appropriate upgrade path based on your current version branch (4.10.x, 4.14.x, or 4.15.x)
  4. 4. Download the corresponding fixed release: 4.10u11, 4.14.2u2, or 4.15u1 from the official Tridium/Honeywell distribution channel
  5. 5. Back up all Niagara configurations, databases, and custom modules before proceeding
  6. 6. Follow the standard Niagara upgrade procedure documented in the Niagara installation guide
  7. 7. After upgrade, verify the cryptographic configuration settings are properly applied
  8. 8. Test critical functionality to ensure the upgrade did not break existing integrations
Caveat Review release notes for any breaking changes between your current version and the target upgrade version; custom modules or integrations may require updates

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

Fix this in Niagara Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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