dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-12897

HIGH · 8.4 CVSS v4.0 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Zero-click 8 weeks old

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
Horner Automation Cscape versions prior to 10.2 SP3 are vulnerable to an Out-of-Bounds Read vulnerability through parsing CSP files. Successful exploitation of this vulnerability could allow an attacker to disclose information and execute arbitrary code.

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

Horner Automation Cscape versions prior to 10.2 SP3 contain an out-of-bounds read vulnerability when parsing CSP project files. This memory corruption issue can allow an attacker to read sensitive information from memory and potentially achieve arbitrary code execution through specially crafted malicious CSP files.

MitigationUsers must update to Horner Cscape version 10.2 SP3 or later to receive the vendor patch. Until updated, exercise extreme caution with untrusted CSP files and consider network isolation of systems running this software.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Horner Cscape is installed
    Search the system for Horner Cscape installation directories or check Programs and Features (Windows) for Horner Automation Cscape.
    Affected if The software is present on the system.
  2. Locate the installed version
    Open the Horner Cscape application and navigate to Help > About, or check the executable file properties (right-click the Cscape.exe file and view Details tab).
    Affected if A version number is displayed.
  3. Compare version to the fixed release
    Compare the installed version to 10.2 SP3. Note that versions prior to 10.2 SP3 (such as 10.2 SP2, 10.1, 10.0, or earlier) are in the affected range.
    Affected if The installed version is earlier than 10.2 SP3 (for example, 10.2 SP2 or lower).
  4. Identify CSP file processing exposure
    Determine if the system handles CSP project files. Check for .csp files in user directories, network shares, or download folders, or monitor for attempts to open CSP files in Cscape.
    Affected if CSP files are opened or processed by the software, as this triggers the vulnerable parsing code.

You are affected if Horner Cscape is installed with a version earlier than 10.2 SP3 and the software processes CSP project files.

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

Users must update to Horner Cscape version 10.2 SP3 or later to receive the vendor patch. Until updated, exercise extreme caution with untrusted CSP files and consider network isolation of systems running this software.

Recommended fix High confidence

Horner Automation Cscape version 10.2 SP3

  1. Identify the currently installed version of Horner Automation Cscape on the system
  2. Obtain Horner Automation Cscape version 10.2 SP3 or later from the official Horner Automation vendor website or authorized distribution channel
  3. Create a backup of all existing Cscape project files (.csp files) and any associated configurations
  4. Uninstall the current version of Horner Automation Cscape from the system
  5. Install version 10.2 SP3 following the vendor's standard installation procedures
  6. After installation, verify that the software version shows 10.2 SP3 or later
  7. Open existing Cscape project files to confirm they load correctly and functionality is intact
  8. Re-scan the environment to confirm the vulnerability is remediated
Caveat Upgrade to the fixed version should maintain backward compatibility with existing CSP project files; however, always test critical projects in a non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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