dbcve.org
Sicam Siapp SdkApplication · Siemens

CVE-2026-25573

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 2.17 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 SICAM SIAPP SDK (All versions < V2.1.7). The affected application builds shell commands with caller-provided strings and executes them. An attacker could influence the executed command, potentially resulting in command injection and full system compromise.

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

The SICAM SIAPP SDK versions prior to V2.1.7 contain a command injection vulnerability where the application constructs shell commands using unsanitized user-supplied input and executes them via the system shell. An attacker who can control the input to these command-building functions can inject arbitrary shell commands, potentially achieving full system compromise with the privileges of the application.

MitigationUpgrade to SICAM SIAPP SDK V2.1.7 or later. As an interim measure, implement strict input validation and whitelist filtering on all data used in command construction, and replace shell command execution with direct process execution APIs that bypass shell interpretation.

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
Sicam Siapp SdkApplication
Affected:< 2.17

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 SICAM SIAPP SDK installation
    Search for Siemens SICAM SIAPP SDK files, libraries, or runtime components on the system. Check common installation directories or review application dependencies that reference 'SICAM SIAPP SDK' or 'Siapp'.
    Affected if The SDK is present on the system
  2. Determine installed SDK version
    Locate version information in SDK metadata, manifest files, DLL/file version properties, or check the product name/version from installed program listings. Compare against the affected range of versions prior to 2.17.
    Affected if The installed version is less than 2.17
  3. Inspect application code for command construction
    Review application source code or binaries that utilize the SICAM SIAPP SDK for instances where shell commands are built using user-supplied data. Look for patterns where input parameters are concatenated into command strings before execution.
    Affected if User-controlled input is passed to command-building functions within the SDK or applications using the SDK

The environment is affected if SICAM SIAPP SDK version 2.17 or later is not installed AND the application uses the SDK's command-building functionality with untrusted user input.

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.17 or later
Fixed in 2.17
Interim mitigation

Upgrade to SICAM SIAPP SDK V2.1.7 or later. As an interim measure, implement strict input validation and whitelist filtering on all data used in command construction, and replace shell command execution with direct process execution APIs that bypass shell interpretation.

Recommended fix High confidence

V2.1.7

  1. 1. Obtain the latest SICAM SIAPP SDK version V2.1.7 or later from the official Siemens download channels (e.g., Siemens Industry Online Support or your Siemens representative).
  2. 2. Ensure all production environments and development systems running vulnerable versions (< V2.1.7) are identified and documented.
  3. 3. Create a complete backup of the current SICAM SIAPP SDK installation and any associated configuration files.
  4. 4. Before deploying the upgrade, review the release notes and upgrade documentation provided with V2.1.7 for any specific migration requirements.
  5. 5. Install SICAM SIAPP SDK version V2.1.7 on all affected systems, following the official installation procedures.
  6. 6. After upgrade, verify that the application functions correctly and that the command injection vulnerability is remediated by testing with previously vulnerable input vectors.
  7. 7. Monitor the system for any abnormal behavior and ensure logging is functioning as expected.

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

Fix this in Sicam Siapp Sdk Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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