Security readout for executives and security teams
Plain-English summary
A network request that is too large can overrun memory in affected NetStaX EtherNet/IP components. An unauthenticated remote party with network access could corrupt memory or crash an industrial device, potentially disrupting operations. Because exploitation requires no credentials or user action and may affect confidentiality, integrity, and availability, exposed deployments warrant urgent remediation.
Executive priority
Treat reachable operational deployments as an urgent remediation item. Prioritize systems whose failure could stop production, affect safety dependencies, or cross network trust boundaries. Fund vendor coordination and controlled maintenance because the vulnerable stack may be embedded within equipment firmware rather than managed as a visible standalone package.
Technical view
NetStaX versions before v5.6.1 may accept a large CIP Class 3 explicit-message request exceeding the application receive buffer without returning an error. This stack-based buffer overflow can cause memory corruption or device failure. CVSS 3.1 rates it 9.8: network-accessible, low complexity, unauthenticated, and requiring no user interaction.
Likely exposure
Exposure exists where products embed pre-v5.6.1 EIPA, EIPA-SECURE, EADK, EADK-SECURE, EIPS, EIPS-SECURE, ESDK, or ESDK-SECURE components and accept reachable Class 3 explicit messaging. Internet or untrusted-network reachability increases urgency. Asset firmware may conceal the underlying library version, requiring confirmation from device suppliers or integrators.
Exploitation context
The supplied sources describe a potential remote attack vector, but provide no evidence of active exploitation; the CVE is not listed as KEV in the bundle. Successful exploitation could corrupt memory or crash a device. Although the CVSS assessment indicates high confidentiality, integrity, and availability impacts, the evidence supplied does not establish reliable code execution.
Researcher notes
CWE-121 applies because an oversized Class 3 explicit-message request can exceed an application-side receive buffer. The absence of a CIP rejection is operationally relevant because senders may receive no warning that processing failed. Product-specific exploitability may depend on integration, memory protections, and network reachability; those details are not established by the supplied evidence.
Mitigation direction
- Upgrade affected NetStaX components and kits to v5.6.1 or later, following Pyramid Solutions guidance.
- Ask equipment vendors whether deployed firmware embeds an affected NetStaX version and obtain their approved update.
- Restrict EtherNet/IP messaging to trusted management and control networks using segmentation and allowlisting.
- Block unnecessary access from enterprise, remote-access, and internet-facing networks until affected systems are updated.
- Apply vendor-recommended compensating controls where operational constraints prevent immediate upgrades.
Validation and detection
- Inventory devices and applications using the listed Adapter or Scanner kits, including secure variants.
- Confirm the embedded NetStaX version through build records, software inventories, integrators, or equipment vendors.
- Map which affected assets accept Class 3 explicit messages from untrusted or broadly accessible networks.
- Verify updated systems report v5.6.1 or later using vendor-supported identification methods.
- Review monitoring and device logs for oversized explicit messages, memory faults, or unexplained restarts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2026-78012 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9icscertCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——icscertVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://pyramidsolutions.com/netstax-v-5-6-1-protecting-against-silent-buffer-overflow-in-ethernet-ip-stack-explicit-messages/CVE reference, icscert
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-07CVE reference, icscert
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-246-07.jsonCVE reference, icscert
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.