**CVE-2025-3943** is a Tridium Niagara Framework flaw, published on 2025-05-22, in which the anti-CSRF refresh token is sent in GET query strings, so it is written to logs and can cross the network in plain Syslog. NVD scores it 7.5. Nozomi Networks Labs used it to open a chain that ends in root code execution on QNX-based Niagara controllers.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
11.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2025-3943 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Tridium Niagara Framework on Windows, Linux and QNX | cpe: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 QNX | cpe: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-3943 as a "Use of GET Request Method With Sensitive Query Strings vulnerability in Tridium Niagara Framework on Windows, Linux, QNX" and in Niagara Enterprise Security, and lists versions 4.10u10, 4.14u1 and 4.15 as affected (NVD). The scores are far apart. NVD's own CVSS 3.1 score is 7.5 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, while Honeywell, the CNA, scores it 4.1 with AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N, because the attack needs a logged-in user and an administrator who follows a link. Honeywell maps it to CWE-598; NVD records NVD-CWE-Other.
Nozomi Networks Labs found the bug in Niagara 4.13 and published the details on 2025-07-23. Workbench sends the CSRF refresh token to the /ord endpoint through the spy function with the GET method, the token stays the same for the whole session, and the administration panel often triggers CSP violation reports that log the full request, token included. Nozomi says the chain needs two conditions: an attacker who can sniff or man-in-the-middle traffic to the Niagara device, and Syslog forwarding "without encryption, a setting which produces a warning on the security dashboard."
From there Nozomi describes the full chain against a station, with a "Niagara-based Tridium Jace 8000" on a local network as its example. The attacker reads the token from Syslog, uses a forged link to set the web.jetty log level to ALL, reads the administrator's JSESSIONID from the next log lines, creates a backdoor administrator, downloads the device's TLS private key, and then uses CVE-2025-3944 for root code execution on the QNX-based operating system. Nozomi adds that, even without that last step, the method compromises both Station and Platform, including on Windows.
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-3943 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.114, percentile 96.1, 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. For this CVE the hardening step that matters is Syslog over TLS: the guide says that as of Niagara 4.13 messages "can be sent over UDP, TCP, or TLS". Our Niagara Fox protocol guide explains where this chain fits next to the plaintext Fox exposure, and CVE-2025-3937 and CVE-2025-3945 are two more CVEs from the same bulletin.
Evidence
- GET request with sensitive query strings in Niagara Framework and Enterprise Security on Windows, Linux, QNX; CPE 4.10u10, 4.14u1, 4.15; NVD Primary CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), NVD-CWE-Other; Honeywell 4.1, CWE-598; fixed releases 4.14.2u2, 4.15.u1, 4.10u.11. — NVD
- Found in 4.13; CSRF refresh token sent via /ord spy with GET, unchanged per session, logged through CSP reports; preconditions are sniffing/MitM and unencrypted Syslog; chain with JACE 8000 scenario ends with CVE-2025-3944 root RCE. — Nozomi Networks Labs: Critical Vulnerabilities Found in Tridium Niagara Framework (2025-07-23)
- FX80, FX90, FX Server at FX 14.10.10 / 14.14.1 and earlier; FX 14.10.10 contains Niagara 4.10u10, FX 14.14.1 contains Niagara 4.14u1; could trigger CVE-2025-3936 through CVE-2025-3945; patches 14.10.11 and 14.14.2; Update A 2025-12-04. — CISA ICSA-25-219-02: Johnson Controls FX Server, FX80 and FX90, Update A (CSAF)
- Affected: Niagara Framework and Enterprise Security 4.10u10, 4.14u1, 4.15; Honeywell score 4.1; upgrade 4.14 deployments to 4.14u2; review Security Dashboard and Hardening Guide. — Honeywell/Tridium Security Bulletin SB 2025-Tridium-1: Niagara software vulnerabilities (PDF)
- As of Niagara 4.13, Syslog messages can be sent over UDP, TCP, or TLS. — Tridium: Niagara 4 Hardening Guide (2025-01-17, PDF)
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.11383 (percentile 96.1), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
- NVD
- Honeywell/Tridium Security Bulletin SB 2025-Tridium-1: Niagara software vulnerabilities (PDF)
- Nozomi Networks Labs: Critical Vulnerabilities Found in Tridium Niagara Framework (2025-07-23)
- CISA ICSA-25-219-02: Johnson Controls FX Server, FX80 and FX90, Update A (CSAF)
- Tridium: Niagara 4 Hardening Guide (2025-01-17, PDF)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Why does NVD score CVE-2025-3943 at 7.5 when Honeywell scores it 4.1?
NVD scored it as a network attack with no privileges or user interaction (AV:N/AC:L/PR:N/UI:N) and high confidentiality impact. Honeywell, the CNA, requires a low-privileged user and user interaction and rates the confidentiality impact low, which gives 4.1 (per NVD and SB 2025-Tridium-1).
What does an attacker need to exploit CVE-2025-3943?
Nozomi Networks Labs lists two conditions: the ability to sniff or man-in-the-middle traffic to the Niagara device, and Syslog forwarding without encryption, which produces a warning on the Niagara Security Dashboard (per Nozomi Networks Labs).
Which Niagara versions fix CVE-2025-3943?
The CVE record names Niagara Framework and Enterprise Security 4.14.2u2, 4.15.u1 and 4.10u.11. Tridium's bulletin tells 4.14 sites to upgrade to 4.14u2 (per NVD and SB 2025-Tridium-1).
Are Johnson Controls FX controllers affected by CVE-2025-3943?
CISA's ICSA-25-219-02 says FX 14.10.10 contains Niagara 4.10u10 and FX 14.14.1 contains Niagara 4.14u1, that its CVE-2025-43867 could trigger CVE-2025-3936 through CVE-2025-3945, and that the FX 14.10.11 and 14.14.2 patches fix the FX80, FX90 and FX Server (per CISA ICSA-25-219-02).
Is CVE-2025-3943 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.114, percentile 96.1, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?