Access of Resource Using Incompatible Type ('Type Confusion') Affecting suricata package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.4% (35th 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-19964526
  • published20 Sept 2026
  • disclosed20 Sept 2026

Introduced: 20 Sep 2026

NewCVE-2026-94083  (opens in a new tab)
CWE-843  (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 before 8.0.7 has a DoH2 type confusion that can cause an invalid free, because cleanup code for the HTTP2 state is executed even though the actual state is HTTP1 (when there is a DoH2 request with an HTTP1 to HTTP2 upgrade). This requires app-layer.protocols.doh2 to be enabled, which is the default in 8.x versions.