dbcve.org
Simatic Pcs NeoApplication · Siemens

CVE-2025-40796

HIGH · 7.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2.15.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 SIMATIC PCS neo V4.1 (All versions), SIMATIC PCS neo V5.0 (All versions), SIMATIC PCS neo V6.0 (All versions < V6.0 SP1 Update 1), User Management Component (UMC) (All versions < V2.15.1.3). Affected products contain a out-of-bounds read vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to cause a denial of service condition.

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 confidence

An out-of-bounds read vulnerability exists in the User Management Component (UMC) of SIMATIC PCS neo V4.1 through V6.0 (prior to SP1 Update 1) and UMC versions prior to V2.15.1.3. This memory safety flaw allows an unauthenticated remote attacker to read beyond allocated buffer boundaries, causing a denial of service condition.

MitigationApply vendor patches: update SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and update UMC to V2.15.1.3 or later. If immediate patching is not feasible, restrict network access to UMC interfaces and monitor for anomalous traffic patterns.

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
Simatic Pcs NeoApplication
Affected:= 4.1= 5.0
User Management ComponentApplication
Affected:< 2.15.1.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 SIMATIC PCS neo installation and version
    Use system inventory tools or check the installed programs list for SIMATIC PCS neo. Obtain the exact version number (e.g., 4.1, 5.0, 6.0).
    Affected if The installed version is 4.1, 5.0, or any version from 4.1 through 6.0 prior to SP1 Update 1.
  2. Identify UMC (User Management Component) version
    Check the installed version of the User Management Component. This may be listed separately in system inventory or within the SIMATIC PCS neo application details.
    Affected if The installed UMC version is prior to V2.15.1.3.
  3. Confirm UMC is network-accessible
    Verify that the UMC service is listening on network ports or accessible remotely. Check firewall rules and service bindings for UMC interfaces.
    Affected if UMC is exposed to network access (unauthenticated remote exploitation requires network accessibility).
  4. Cross-reference versions against advisory ranges
    Compare your installed SIMATIC PCS neo version (4.1 through 6.0) and UMC version (anything below 2.15.1.3) against the affected ranges stated in the CVE.
    Affected if Either SIMATIC PCS neo is below V6.0 SP1 Update 1, or UMC is below V2.15.1.3, or both conditions are true.

You are affected if your environment runs any version of SIMATIC PCS neo from V4.1 through V6.0 prior to SP1 Update 1, or runs UMC prior to V2.15.1.3, and the UMC component is network-accessible.

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 2.15.1.3 or later
Fixed in 2.15.1.3
Interim mitigation

Apply vendor patches: update SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and update UMC to V2.15.1.3 or later. If immediate patching is not feasible, restrict network access to UMC interfaces and monitor for anomalous traffic patterns.

Recommended fix Moderate confidence

UMC >= V2.15.1.3; SIMATIC PCS neo V6.0 >= V6.0 SP1 Update 1; Legacy versions V4.1/V5.0 should migrate to V6.0

  1. Upgrade User Management Component (UMC) to version 2.15.1.3 or higher
  2. For SIMATIC PCS neo V6.0: Upgrade to V6.0 SP1 Update 1 or higher
  3. For SIMATIC PCS neo V4.1 and V5.0: Upgrade to a supported newer version (V6.0 with SP1 Update 1 recommended)
  4. After upgrade, verify the UMC component is running the patched version
  5. Test that the User Management functionality operates normally post-upgrade
Caveat Users on V4.1/V5.0 may need full version migration to V6.0 which could require compatibility testing of custom applications

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

Fix this in Simatic Pcs Neo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40796 — 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-2025-40796 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