Homepage

NULL Pointer Dereference Affecting kuma-envoy-1.38 package, versions <1.38.4-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.74% (54th 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-MINIMOSLATEST-KUMAENVOY138-20269016
  • published30 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 21 Sep 2026

NewCVE-2026-48521  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kuma-envoy-1.38 to version 1.38.4-r0 or higher.

NVD Description

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

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's ProdClusterManagerFactory::allocateConnPool dereferences transport_socket_options while selecting an HTTP/3 connection pool without first checking whether the pointer is null. LoadBalancerContext implementations used by synthetic, mirror, health-check, and async-client calls can return no transport-socket options. With auto_config and HTTP/3 enabled, routine traffic reaching one of those contexts can crash an Envoy worker. The relevant scope boundary is that the affected branch requires HTTP/3 in the protocol set and a context that supplies no transport-socket options. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.