Vulnerability in Niagara Framework (CVE-2026-11804)
Summary
Vulnerability in Niagara Framework (CVE-2026-11804). Confidential information can be exposed externally.
Original description
The description as published by the source.
Improper handling of insufficient permissions or privileges vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Privilege Abuse.
This issue affects Niagara Framework: before 4.14.6, before 4.15.5; Niagara Enterprise Security: before 4.14.6, before 4.15.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-11804 has been found in Niagara Framework.
Confidential information can be exposed externally. CVSS score: 5.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Niagara Framework CVE-2026-11804" on the vendor's site.
CVE-2026-11804 (Niagara Framework) — CWE-280 / CVSS v3 5.2
Attack vector: adjacent-network / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-280) exists in Niagara Framework.
Check the vendor advisory for the affected versions of Niagara Framework.
Severity: Medium (CVSS 5.2/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Niagara Framework を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web psirt@honeywell.com
- web psirt@honeywell.com
- web nvd.nist.gov
- web github.com