dbcve.org
Sinec NmsApplication · Siemens

CVE-2026-25655

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 4.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A vulnerability has been identified in SINEC NMS (All versions < V4.0 SP2). The affected application permits improper modification of a configuration file by a low-privileged user. This could allow an attacker to load malicious DLLs, potentially leading to arbitrary code execution with administrative privilege.(ZDI-CAN-28107)

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 · moderate confidence

SINEC NMS allows low-privileged users to modify a configuration file that controls DLL loading. An attacker can inject a malicious DLL path into this configuration, which gets loaded when the application runs with administrative privileges, achieving arbitrary code execution.

MitigationUpgrade SINEC NMS to version V4.0 SP2 or later to obtain the patched version that enforces proper authorization controls on configuration file modification.

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
Sinec NmsApplication
Affected:< 4.0= 4.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SINEC NMS installation and version
    Check the installed SINEC NMS version using system utilities (e.g., 'Get-ItemProperty' in PowerShell for Windows, or check the product's About/Version dialog)
    Affected if The installed version is lower than V4.0 SP2 or exactly V4.0 (i.e., < 4.0 or = 4.0)
  2. Locate the DLL loading configuration file
    Identify configuration files related to DLL search paths or module loading within the SINEC NMS installation directory. Common locations include config or settings subdirectories.
    Affected if The configuration file controlling DLL loading exists in the SINEC NMS installation
  3. Verify configuration file permissions
    Check file system permissions on the identified DLL loading configuration file (e.g., using 'icacls' on Windows or 'ls -l' on Linux) to determine if low-privileged users have write access
    Affected if Low-privileged or non-administrative users have write permissions to the configuration file
  4. Confirm SINEC NMS runs with elevated privileges
    Check the service configuration or startup method for SINEC NMS to determine if it runs under an administrative or SYSTEM account
    Affected if SINEC NMS is configured to run with administrative or elevated SYSTEM privileges

You are affected if SINEC NMS version is < 4.0 or = 4.0, the DLL loading configuration file is writable by low-privileged users, and the application runs with administrative privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.0 or later
Fixed in 4.0
Interim mitigation

Upgrade SINEC NMS to version V4.0 SP2 or later to obtain the patched version that enforces proper authorization controls on configuration file modification.

Recommended fix High confidence

V4.0 SP2

  1. 1. Identify the current installed version of SINEC NMS by checking the application or system information.
  2. 2. Review the SINEC NMS V4.0 SP2 release notes and documentation for any breaking changes or migration requirements.
  3. 3. Perform a full backup of the current SINEC NMS configuration, database, and any custom settings.
  4. 4. If possible, test the upgrade in a non-production environment first to verify compatibility.
  5. 5. Upgrade SINEC NMS to version V4.0 SP2 or later following the official Siemens upgrade documentation.
  6. 6. After upgrade, verify the application starts correctly and all services are running.
  7. 7. Confirm the configuration file permissions have been properly set and no unauthorized modifications are possible.
  8. 8. Validate that the DLL hijacking vulnerability is resolved by checking that the application only loads DLLs from secure locations.
Caveat Review Siemens release notes for V4.0 SP2 for any configuration or feature changes; some legacy settings may require adjustment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sinec Nms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25655 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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