Security Advisory

CVE-2025-3937: Niagara Weak Password Hashing

Last updated:
  • CVE-2025-3937

**CVE-2025-3937** is a weak password hashing flaw in Tridium Niagara Framework and Niagara Enterprise Security, published on 2025-05-22: passwords are hashed with too little computational effort (CWE-916), so stolen hashes are cheaper to crack. It affects 4.10u10, 4.14u1 and 4.15 on Windows, Linux and QNX. NVD scores it 9.8, Honeywell 7.7.

Vulnerability summary

CVSS base score

9.8

Critical severity

EPSS score (FIRST)

0.3%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2025-3937 · Source: NVD

Affected components

ComponentCPEVersion range
Tridium Niagara Framework on Windows, Linux and QNXcpe:2.3:a:tridium:niagara:*:*:*:*:*:*:*:*affected: 4.10u10, 4.14u1 and 4.15 (NVD CPE, SB 2025-Tridium-1); fixed in 4.10u.11, 4.14.2u2 and 4.15.u1 per the CVE record
Tridium Niagara Enterprise Security on Windows, Linux and QNXcpe:2.3:a:tridium:niagara_enterprise_security:*:*:*:*:*:*:*:*affected: 4.10u10, 4.14u1 and 4.15 (NVD CPE, SB 2025-Tridium-1); fixed in 4.10u.11, 4.14.2u2 and 4.15.u1 per the CVE record
Johnson Controls FX80, FX90 and FX Server (bundle Niagara 4.10u10 / 4.14u1)—FX 14.10.10 and FX 14.14.1 and earlier per CISA ICSA-25-219-02 (filed as CVE-2025-43867); patches FX 14.10.11 and 14.14.2

What does this mean for affected devices?

NVD describes CVE-2025-3937 as a "Use of Password Hash With Insufficient Computational Effort vulnerability in Tridium Niagara Framework on Windows, Linux, QNX" and in Niagara Enterprise Security that "allows Cryptanalysis", with CWE-916 from both NVD and Honeywell (NVD). NVD's own CVSS 3.1 score is 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Honeywell, the CNA, scores it 7.7 with AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N: a low-privileged user is needed, and the impact is on confidentiality. The configuration covers releases 4.10u10, 4.14u1 and 4.15 on all three operating systems, so it applies to Niagara on servers and on QNX-based devices alike.

Nozomi Networks Labs puts CVE-2025-3937 at the top of its table of ten CVEs, at 7.7. The researchers found the issues in Niagara 4.13 and say they are fully exploitable when a system is misconfigured, with an attacker on the same network. Neither Nozomi nor Tridium publishes the hash algorithm. Tridium's bulletin SB 2025-Tridium-1 lists "updated some cryptographic parameters to accommodate latest recommendations" among the fixes. A cheap hash matters once an attacker holds the stored hashes: each password guess costs less, so short or common passwords fall faster.

Password strength is the part a site controls. The Niagara 4 Hardening Guide says password strength is enforced by the Password Strength property and "can be increased, it should not be reduced", and that "each JACE is shipped with a default system passphrase" that must be changed at commissioning. After the upgrade, consider changing passwords that may have been exposed, since the fix does not undo a hash that has already been copied.

Johnson Controls ships the same code in its own building controllers. CISA's advisory ICSA-25-219-02, Update A of 2025-12-04 (CSAF), lists the FX80 and FX90 controllers and FX Server at FX 14.10.10 and FX 14.14.1 and earlier under CVE-2025-43867, notes that "FX 14.10.10 contains Niagara 4.10u10" and "FX 14.14.1 contains Niagara 4.14u1", and warns that exploiting it "could trigger CVEs CVE-2025-3936 through CVE-2025-3945". The fix there is the FX 14.10.11 or 14.14.2 patch from the Johnson Controls software portal.

CVE-2025-3937 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0034, percentile 27.6, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

Tridium's bulletin SB 2025-Tridium-1 lists Niagara Framework and Enterprise Security 4.10u10, 4.14u1 and 4.15 as affected and tells 4.14 sites to move to 4.14u2; the CVE record names 4.14.2u2, 4.15.u1 and 4.10u.11 as the fixed releases. The bulletin also asks sites to review the Security Dashboard for warnings and to follow the Niagara 4 Hardening Guide. Our Niagara Fox protocol guide covers the batch and the hardening settings, and CVE-2025-3943 and CVE-2025-3944 are the two bugs Nozomi chained into a full device takeover.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

Related advisories

Sources

  1. NVD
  2. Honeywell/Tridium Security Bulletin SB 2025-Tridium-1: Niagara software vulnerabilities (PDF)
  3. Nozomi Networks Labs: Critical Vulnerabilities Found in Tridium Niagara Framework (2025-07-23)
  4. CISA ICSA-25-219-02: Johnson Controls FX Server, FX80 and FX90, Update A (CSAF)
  5. Tridium: Niagara 4 Hardening Guide (2025-01-17, PDF)
  6. CISA KEV
  7. FIRST EPSS

Frequently asked questions

Which platforms does CVE-2025-3937 affect?

Niagara Framework and Niagara Enterprise Security 4.10u10, 4.14u1 and 4.15 on Windows, Linux and QNX (per NVD).

Which hash algorithm does Niagara use?

Neither the CVE record, Tridium's bulletin nor Nozomi's write-up names it. The bulletin only says the fixes "updated some cryptographic parameters to accommodate latest recommendations" (per SB 2025-Tridium-1).

Why is CVE-2025-3937 9.8 at NVD but 7.7 at Honeywell?

NVD scored it with no privileges required and high impact on confidentiality, integrity and availability. Honeywell requires a low-privileged user, sets scope to changed and rates only confidentiality as high (per NVD).

Does upgrading Niagara fix CVE-2025-3937 completely?

The upgrade to 4.14.2u2, 4.15.u1 or 4.10u.11 fixes the software (per NVD). A hash copied before the upgrade can still be cracked offline, so changing exposed passwords and keeping the Password Strength setting high, as the Niagara 4 Hardening Guide advises, still matters.

Is CVE-2025-3937 in the CISA KEV catalog?

No, as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0034, percentile 27.6, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).