Improper Check for Unusual or Exceptional Conditions Affecting kuma-envoy-fips-1.38 package, versions <1.38.4-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.62% (48th 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-KUMAENVOYFIPS138-20268322
  • published30 Sept 2026
  • disclosed21 Sept 2026

Introduced: 21 Sep 2026

NewCVE-2026-73549  (opens in a new tab)
CWE-754  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kuma-envoy-fips-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-fips-1.38 package and not the kuma-envoy-fips-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 Utility::copyInternetAddressAndPort and QUIC client-address paths reconstruct scoped IPv6 addresses through addressAsString and Ipv6Instance. The string includes a percent scope identifier that inet_pton cannot parse, causing an exception or abort. Kernel-provided scoped IPv6 destinations in ORIGINAL_DST transparent-proxy deployments, and affected QUIC connection paths, can therefore terminate the process. The relevant scope boundary is that the HTTP use_http_header override rejects scoped addresses earlier; the advisory's crash path requires a kernel-provided original destination or the affected QUIC path. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.