CVE-2026-20797: Copeland XWEB and XWEB Pro Stack-based Buffer Overflow
A stack based buffer overflow exists in an API route of XWEB Pro version
1.12.1 and prior, enabling unauthenticated attackers to cause stack
corruption and a termination of the program.
Security readout for executives and security teams
Plain-English summary
CVE-2026-20797 is a medium-severity flaw in Copeland XWEB Pro 1.12.1 and prior. An unauthenticated attacker on an adjacent network could crash the affected program by triggering stack corruption. The cited impact is availability loss, not data theft or system takeover.
Executive priority
Treat this as a moderate operational resilience issue. Prioritize validation in environments where XWEB Pro supports important facility or operational systems, especially if adjacent network access is broadly available.
Technical view
The issue is a CWE-121 stack-based buffer overflow in an XWEB Pro API route. CVSS 3.1 is 4.3: adjacent network, low complexity, no privileges, no user interaction, unchanged scope, no confidentiality or integrity impact, and low availability impact.
Likely exposure
Likely exposure is limited to organizations running Copeland XWEB Pro 1.12.1 or prior where the affected API is reachable from adjacent network segments. The source bundle lists XWEB 300D PRO, 500D PRO, and 500B PRO, but version and CPE details are incomplete.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is unauthenticated and low complexity, but the CVSS vector is adjacent network, and the documented impact is program termination rather than compromise.
Researcher notes
Evidence supports denial-of-service risk through stack corruption in an API route. The bundle does not provide exploit details, proof of active exploitation, precise CPEs, or a specific patched version, so remediation should track Copeland and CISA guidance.
Mitigation direction
Check Copeland System Software Update for vendor-approved updates or advisories.
Review CISA ICSA-26-057-10 for current mitigation guidance.
Inventory XWEB Pro deployments and identify versions 1.12.1 or prior.
Restrict access to XWEB Pro interfaces to trusted administrative networks.
Validation and detection
Confirm whether XWEB Pro is deployed and record exact software versions.
Map which adjacent network segments can reach XWEB Pro API interfaces.
Compare deployed versions against Copeland and CISA advisory details.
Monitor affected services for unexpected termination or instability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.