Insufficient Comparison Affecting suricata package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.44% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-SURICATA-19683878
  • published11 Sept 2026
  • disclosed18 Sept 2026

Introduced: 11 Sep 2026

NewCVE-2026-57222  (opens in a new tab)
CWE-697  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest suricata.

NVD Description

Note: Versions mentioned in the description apply only to the upstream suricata package and not the suricata package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.17 and 8.0.6, crafted IPv4 and IPv6 address pairs can collide in the IPPair hash because src/ippair.c did not compare the IP address family before reusing IPPair-backed state. This can apply state from one IP family to another for xbits track ip_pair, FTP data expectations, and, on the 7.0 release line, thresholding, detection_filter, and rate_filter rules using track by_both, causing incorrect detection state. This issue is fixed in versions 8.0.6 and 7.0.17.