Security readout for executives and security teams
Plain-English summary
Suricata sensors can be crashed by specially crafted DCERPC network traffic because affected versions may buffer fragments without a limit. The business impact is loss of IDS/IPS/NSM visibility or enforcement, not data theft from Suricata itself. Upgrade priority is high for environments monitoring DCERPC, SMB, Windows RPC, or untrusted network traffic.
Executive priority
Treat as high priority for security monitoring infrastructure. A successful attack can blind or disable Suricata-based detection or prevention at a critical network point. Prioritize internet-facing, perimeter, data center, and Windows-heavy network segments first.
Technical view
CVE-2026-22258 affects OISF Suricata before 7.0.14 and 8.0.0 through 8.0.2. Crafted DCERPC traffic can trigger unbounded buffer growth, causing memory exhaustion and process termination. Reported for DCERPC over UDP; TCP and SMB are believed vulnerable. Default DCERPC/TCP stream depth of 1MiB should reduce exposure.
Likely exposure
Exposed Suricata deployments inspecting DCERPC/UDP are most directly at risk. DCERPC over SMB may be relevant because SMB stream reassembly depth is unlimited by default. DCERPC/TCP default configuration is less exposed due to the default 1MiB stream depth, per the advisory.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. The flaw is network-reachable, low-complexity, unauthenticated, and availability-impacting. Successful exploitation would likely kill or destabilize the Suricata process, reducing monitoring or blocking coverage.
Researcher notes
The advisory attributes the issue to unbounded fragment buffering and maps it to CWE-400 and CWE-770. Evidence says DCERPC/UDP was reported, while TCP and SMB are believed vulnerable. Avoid assuming exploit availability; no cited source confirms exploitation in the wild.
Mitigation direction
- Upgrade Suricata to 8.0.3 or 7.0.14 where applicable.
- For DCERPC/UDP, disable the parser if operationally acceptable.
- For DCERPC/TCP, keep stream.reassembly.depth limited.
- For DCERPC/SMB, consider setting stream.reassembly.depth, accepting possible SMB visibility loss.
- Review OISF advisory for current vendor guidance and workaround details.
Validation and detection
- Inventory Suricata versions and identify instances below 7.0.14 or 8.0.3.
- Check whether DCERPC, SMB, and UDP parsing are enabled on sensors.
- Review stream.reassembly.depth settings for TCP and SMB inspection paths.
- Monitor Suricata process restarts, memory exhaustion events, and sensor coverage gaps.
- Confirm upgraded sensors report fixed versions after deployment.
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-22258 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-289c-h599-3xcxCVE reference · x_refsource_CONFIRM
- https://github.com/OISF/suricata/commit/39d8c302af3422a096b75474a4f295a754ec6a74CVE reference · x_refsource_MISC
- https://github.com/OISF/suricata/commit/f82a388d0283725cb76782cf64e8341cab370830CVE reference · x_refsource_MISC
- https://redmine.openinfosecfoundation.org/issues/8182CVE 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.