How severe is CVE-2025-3938?

CVE-2025-3938 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-3938 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-3938?

CVE-2025-3938 primarily affects Tridium Niagara. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-3938?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-3938 have an EU (EUVD) identifier?

Yes. CVE-2025-3938 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16121.

When was CVE-2025-3938 published?

CVE-2025-3938 was published on 2025-05-22 and last updated on 2026-06-17.

CVE-2025-3938

CVE-2025-3938 is a medium-severity vulnerability in Tridium Niagara with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-16121
Weakness: CWE-327
Affected product: Tridium Niagara
Published: 2025-05-22
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-3938?: 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.
How severe is CVE-2025-3938?: CVE-2025-3938 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-3938 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-3938?: CVE-2025-3938 primarily affects Tridium Niagara. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-3938?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-3938 have an EU (EUVD) identifier?: Yes. CVE-2025-3938 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16121.
When was CVE-2025-3938 published?: CVE-2025-3938 was published on 2025-05-22 and last updated on 2026-06-17.

References

Affected products (6)

cpe:2.3:a:tridium:niagara:4.10u10:*:*:*:*:*:*:*
cpe:2.3:a:tridium:niagara:4.14u1:*:*:*:*:*:*:*
cpe:2.3:a:tridium:niagara:4.15:*:*:*:*:*:*:*
cpe:2.3:a:tridium:niagara_enterprise_security:4.10u10:*:*:*:*:*:*:*
cpe:2.3:a:tridium:niagara_enterprise_security:4.14u1:*:*:*:*:*:*:*
cpe:2.3:a:tridium:niagara_enterprise_security:4.15:*:*:*:*:*:*:*

More vulnerabilities in Tridium Niagara

CVE-2017-16748 — Critical (CVSS 9.8): An attacker can log into the local Niagara platform (Niagara AX Framework Versions 3.8 and prior or Niagara 4 Framework…
CVE-2025-3937 — High (CVSS 7.7): Use of Password Hash With Insufficient Computational Effort vulnerability in Tridium Niagara Framework on Windows,…
CVE-2025-3945 — High (CVSS 7.2): Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Tridium Niagara…
CVE-2025-3944 — High (CVSS 7.2): Incorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on QNX, Tridium…
CVE-2017-16744 — High (CVSS 7.2): A path traversal vulnerability in Tridium Niagara AX Versions 3.8 and prior and Niagara 4 systems Versions 4.4 and…
CVE-2025-3936 — Medium (CVSS 6.5): Incorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on Windows, Tridium…

All CVEs affecting Tridium Niagara →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →