dbcve.org
Sicam Siapp SdkApplication · Siemens

CVE-2026-25570

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 SICAM SIAPP SDK does not perform checks on input values potentially resulting in stack overflow. This could allow an attacker to perform code execution and denial of service.

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 SICAM SIAPP SDK versions prior to V2.1.7 lack proper input validation checks, allowing potentially malicious input values to trigger a stack overflow condition. This memory corruption vulnerability could enable an attacker to achieve arbitrary code execution or cause a denial of service on the affected system.

MitigationUpgrade to SICAM SIAPP SDK V2.1.7 or later which addresses the input validation vulnerability. If immediate patching is not possible, implement input bounds checking and validation routines before processing any external input.

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
    Locate the SICAM SIAPP SDK installation directory and check for version information files such as version.txt, About dialog, or SDK release notes. Common locations include C:\Program Files\Siemens\SICAM\SIAPP or similar installation paths.
    Affected if The installed version is found to be below V2.1.7 (or V2.17 if using three-digit versioning)
  2. Verify SDK version in project references
    If you have source code using this SDK, check the project references or dependency manifests (packages.config, .csproj, or similar) for the SICAM SIAPP SDK version number.
    Affected if The referenced SDK version is less than 2.1.7
  3. Determine if external input is processed
    Identify whether applications or services built with this SDK process external input from network sources, user inputs, or file imports that could reach the SDK's parsing functions.
    Affected if External or untrusted input is processed by code using this vulnerable SDK version
  4. Check for input validation layer
    Inspect application code that uses the SDK to determine if custom input validation or bounds checking is performed before passing data to SDK functions.
    Affected if No input validation layer exists and the SDK version is vulnerable
  5. Audit SDK configuration files
    Review any configuration files or settings related to the SICAM SIAPP SDK installation for security-related parameters or input handling settings.
    Affected if Configuration allows unrestricted input processing without validation

You are affected if your installed SICAM SIAPP SDK version is below V2.1.7 and your application processes external input that reaches SDK functions without additional validation.

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 which addresses the input validation vulnerability. If immediate patching is not possible, implement input bounds checking and validation routines before processing any external input.

Recommended fix High confidence

SICAM SIAPP SDK V2.1.7

  1. 1. Navigate to the Siemens cert-portal website or official Siemens support channels to obtain the SICAM SIAPP SDK version 2.1.7
  2. 2. Verify the integrity of the downloaded package using checksums if provided
  3. 3. Backup your current project configurations and any custom implementations using the existing SDK
  4. 4. Uninstall or remove the current SICAM SIAPP SDK version
  5. 5. Install version 2.1.7 of the SICAM SIAPP SDK
  6. 6. Rebuild and recompile your application with the updated SDK
  7. 7. Test the application thoroughly to ensure functionality is maintained
  8. 8. Validate that input validation is now properly implemented in the updated SDK
Caveat Review release notes for any API changes between your current version and V2.1.7 that may require code adjustments

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

Fix this in Sicam Siapp Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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