CVE-2025-3936
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 · uneditedIncorrect Permission Assignment for Critical Resource vulnerability in Tridium Niagara Framework on Windows, Tridium Niagara Enterprise Security on Windows allows Exploiting Incorrectly Configured Access Control Security Levels. 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 confidenceA critical incorrect permission assignment vulnerability in Tridium Niagara Framework and Niagara Enterprise Security on Windows allows exploitation of incorrectly configured access control security levels. This authorization weakness enables attackers to access critical resources due to improperly set permissions.
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= 4.10u10= 4.14u1= 4.15= 4.10u10= 4.14u1= 4.15CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Niagara Framework versionCheck the Niagara installation directory for version information. Typically found in the niagara home folder, check for a version file or examine the 'about' dialog in the Niagara Workbench. On Windows, the version is often visible in the installer or in the program files directory structure.Affected if The installed version matches 4.10u10, 4.14u1, or 4.15 exactly (these are the vulnerable versions listed).
-
Confirm the Niagara Enterprise Security component versionIf Niagara Enterprise Security is installed, check its version through the Niagara Workbench or the Windows installer. Navigate to the Enterprise Security module and locate the version information.Affected if The Enterprise Security version matches 4.10u10, 4.14u1, or 4.15 exactly.
-
Inspect access control security level configurationIn the Niagara Workbench, navigate to the Security settings or Access Control configuration. Look for the configured security levels for user roles and permissions on critical resources. Check if any security level is set to an inappropriately low setting that grants excessive access.Affected if Security levels are set to permit unauthorized access to critical resources, or if default security levels were not properly hardened during installation.
-
Review Windows file system permissions on Niagara directoriesUsing Windows File Explorer or icacls, inspect the permissions on the Niagara installation directory (typically under Program Files or ProgramData). Check if non-admin users have been granted excessive read/write permissions to configuration files or system directories.Affected if Users with standard privileges have been granted permissions beyond what is required, allowing potential exploitation of the authorization weakness.
A system is affected if it runs any of the specific versions (4.10u10, 4.14u1, or 4.15) of Tridium Niagara or Niagara Enterprise Security AND has access control security levels configured in a way that grants improper permissions to non-administrative users.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to vendor-recommended versions (4.14.2u2, 4.15.u1, or 4.10u.11) and verify access control security levels are properly configured post-upgrade.
Upgrade to Niagara Framework or Niagara Enterprise Security version 4.14.2u2, 4.15.u1, or 4.10u.11
- 1. Identify the current Niagara Framework or Niagara Enterprise Security version running on the Windows system
- 2. Backup all Niagara configuration data, databases, and station files according to vendor backup procedures
- 3. Download the appropriate fixed version (4.14.2u2, 4.15.u1, or 4.10u.11) from the official Tridium/Honeywell distribution channel
- 4. Review the official Niagara upgrade guide for your current version to target version migration path
- 5. Stop all Niagara services on the Windows host
- 6. Install the upgraded Niagara Framework or Enterprise Security version
- 7. Verify the upgraded version matches one of the fixed releases: 4.14.2u2, 4.15.u1, or 4.10u.11
- 8. Start Niagara services and confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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