Homepage

Interpretation Conflict Affecting kuma-envoy-fips-1.36 package, versions <1.36.10-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.51% (42nd 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-KUMAENVOYFIPS136-20268292
  • published30 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 21 Sep 2026

NewCVE-2026-73553  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kuma-envoy-fips-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-fips-1.36 package and not the kuma-envoy-fips-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, When ignore_path_parameters_in_path_matching is enabled, Envoy's router strips the semicolon suffix before matching but the RBAC url_path matcher evaluates the raw path. A downstream request such as /admin;x can therefore miss a DENY rule for /admin while the router still selects the protected /admin backend. The inconsistent canonicalization allows an unauthenticated client to bypass path-based authorization. The relevant scope boundary is that the route option and a path-based RBAC rule must both be present, and the protected route must match after stripping. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.