Security readout for executives and security teams
Plain-English summary
CVE-2026-22259 can let specially crafted DNP3 network traffic make Suricata consume excessive memory. Suricata may slow down or be killed by the operating system, reducing IDS/IPS monitoring availability. This matters most where Suricata inspects DNP3 traffic, commonly associated with industrial control environments.
Executive priority
Prioritize within normal high-severity patch cycles, faster for industrial or DNP3-monitoring environments. Business impact is loss or degradation of network security monitoring, not data theft or code execution based on current sources.
Technical view
Suricata before 7.0.14 and 8.0.0 through 8.0.2 has unbounded transaction growth while parsing DNP3. The CVSS 3.1 score is 7.5: network exploitable, low complexity, no privileges or user interaction, availability impact only. Patched versions are 7.0.14 and 8.0.3.
Likely exposure
Exposure is limited to deployments running affected Suricata versions with the DNP3 parser enabled or otherwise parsing DNP3 traffic. The advisory notes DNP3 is disabled by default, so many installations may not be exposed unless explicitly configured.
Exploitation context
The provided sources describe specially crafted traffic causing memory exhaustion. They do not state active exploitation, and this CVE is not marked KEV in the supplied data. No public exploit status is established from the provided sources.
Researcher notes
Key constraints are parser state growth and availability impact. Sources identify CWE-400 and CWE-770. Review the OISF advisory, linked commits, and Redmine issue for implementation details. Avoid assuming exposure where DNP3 remains disabled by default.
Mitigation direction
- Upgrade Suricata to 7.0.14 or 8.0.3 as applicable.
- If unable to upgrade, disable the DNP3 parser in suricata.yaml.
- Confirm whether DNP3 parsing is needed before re-enabling it.
- Monitor Suricata memory use until patched or DNP3 is disabled.
Validation and detection
- Inventory Suricata deployments and record exact versions.
- Check whether DNP3 parser configuration is enabled.
- Review traffic scope to see if DNP3 reaches Suricata sensors.
- Verify upgraded sensors report version 7.0.14 or 8.0.3.
- Watch for Suricata restarts or OOM-killer events in logs.
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-400: 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 lookupCWE-770: 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-22259 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
CVSS vector scores
1 official scoreWe 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:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OISF/suricata/security/advisories/GHSA-878h-2x6v-84q9CVE reference · x_refsource_CONFIRM
- https://github.com/OISF/suricata/commit/50cac2e2465ca211eabfa156623e585e9037bb7eCVE reference · x_refsource_MISC
- https://github.com/OISF/suricata/commit/63225d5f8ef64cc65164c0bb1800730842d54942CVE reference · x_refsource_MISC
- https://redmine.openinfosecfoundation.org/issues/8181CVE reference · x_refsource_MISC
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.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.