Homepage

Improper Input Validation 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.47% (39th 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-20267886
  • published30 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 21 Sep 2026

NewCVE-2026-73552  (opens in a new tab)
CWE-20  (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, Envoy HTTP RBAC accepts RFC-valid opaque header bytes but evaluates safe_regex values with RE2's UTF-8 subject semantics. A downstream client can preserve a prohibited marker and add an unrelated obs-text octet, causing RE2::FullMatch to return false and a negative RBAC policy to treat the invalid subject as an ordinary no-match. A byte-oriented route matcher can still observe the marker, allowing the request to reach a route intended to be denied. The relevant scope boundary is that plain positive ALLOW regexes normally fail closed, and exact, prefix, suffix, and contains matchers are not shown to have this subject-domain failure. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.