dbcve.org
Sinamics G220 FirmwareOperating system · Siemens

CVE-2025-40594

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 SINAMICS G220 V6.4 (All versions < V6.4 HF2), SINAMICS S200 V6.4 (All versions < V6.4 HF7), SINAMICS S210 V6.4 (All versions < V6.4 HF2). The affected devices allow a factory reset to be executed without the required privileges due to improper privilege management as well as manipulation of configuration data because of leaked privileges of previous sessions. This could allow an unauthorized attacker to escalate their privileges.

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

The SINAMICS G220, S200, and S210 drives contain a privilege escalation vulnerability where factory reset can be executed without proper authentication due to improper privilege management and session-based privilege leakage. An unauthenticated attacker could exploit this to gain elevated privileges and manipulate device configuration.

MitigationUpdate affected devices to the specified hotfix versions (G220 and S210 to V6.4 HF2 or later, S200 to V6.4 HF7 or later) to remediate the vulnerability.

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
Sinamics G220 FirmwareOperating system
Affected:= 6.4
Sinamics S200 FirmwareOperating system
Affected:= 6.4
Sinamics S210 FirmwareOperating system
Affected:= 6.4

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
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 checks

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

  1. Identify the Sinamics drive model
    Check the device label, web interface, or management console to confirm the exact model (G220, S200, or S210)
    Affected if The model is any of G220, S200, or S210
  2. Check the installed firmware version
    Access the device web interface, STARTER/SINAMICS Startdrive software, or device menu to retrieve the firmware version
    Affected if The firmware version is exactly 6.4 (not HF2 or later for G220/S210, not HF7 or later for S200)
  3. Verify authentication enforcement on factory reset
    Attempt to access the factory reset function without credentials or inspect the security settings to confirm authentication is required
    Affected if Factory reset executes or is accessible without valid authentication
  4. Inspect session privilege handling
    Check if session tokens from previous authenticated sessions retain elevated privileges after logout or if privilege escalation occurs without fresh authentication
    Affected if Sessions exhibit privilege leakage or allow unauthorized elevation of privileges

You are affected if you have a Sinamics G220, S200, or S210 device running firmware version 6.4 without the hotfix (HF2 for G220/S210 or HF7 for S200), and the device allows factory reset or configuration changes without proper authentication due to session privilege leakage.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected devices to the specified hotfix versions (G220 and S210 to V6.4 HF2 or later, S200 to V6.4 HF7 or later) to remediate the vulnerability.

Recommended fix Moderate confidence

Sinamics G220: V6.4 HF2 or later | Sinamics S200: V6.4 HF7 or later | Sinamics S210: V6.4 HF2 or later

  1. 1. Identify the exact firmware version currently installed on the affected Sinamics device (G220, S200, or S210)
  2. 2. For Sinamics G220: Upgrade firmware to version V6.4 HF2 or later
  3. 3. For Sinamics S200: Upgrade firmware to version V6.4 HF7 or later
  4. 4. For Sinamics S210: Upgrade firmware to version V6.4 HF2 or later
  5. 5. Obtain the firmware update from official Siemens sources (cert-portal.siemens.com or Siemens Industry Online Support)
  6. 6. Follow Siemens standard firmware upgrade procedure for the specific Sinamics model, ensuring proper backup of current configuration
  7. 7. After upgrade, verify that the device operates correctly and test that privilege management functions properly
  8. 8. Confirm the new firmware version is correctly installed
Caveat Firmware updates may require testing in a non-production environment first; ensure compatibility with connected control systems

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

Fix this in Sinamics G220 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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