Homepage

Improper Input Validation Affecting kuma-envoy-1.36 package, versions <1.36.10-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.48% (40th 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-KUMAENVOY136-20268910
  • published30 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 21 Sep 2026

NewCVE-2026-73513  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-416  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kuma-envoy-1.36 to version 1.36.10-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kuma-envoy-1.36 package and not the kuma-envoy-1.36 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 optional oghttp2 upstream HTTP/2 codec accepts a response trailer HEADERS frame without END_STREAM. Envoy completes and deferred-deletes the ActiveRequest while oghttp2 keeps the stream open, leaving ClientStreamImpl with a dangling response_decoder_ reference. A later frame on the stream can dispatch through the freed object and crash the process. The relevant scope boundary is that the default nghttp2 codec rejects the malformed trailers, and the trigger is upstream-only with oghttp2 enabled. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.