Homepage

Authentication Bypass Affecting ecs-service-connect-agent package, versions <0:v1.39.1.0-1.amzn2023

Severity

 Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.38% (30th 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-AMZN2023-ECSSERVICECONNECTAGENT-19821440
  • published15 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 15 Sep 2026

CVE-2026-73511  (opens in a new tab)
CWE-289  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 ecs-service-connect-agent to version 0:v1.39.1.0-1.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2149.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ecs-service-connect-agent package and not the ecs-service-connect-agent package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 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 normally matches the raw request path, while servlet backends such as Apache Tomcat strip semicolon matrix parameters from each path segment before resolving the resource. Envoy's ignore_path_parameters_in_path_matching option instead truncates at the first semicolon and still does not match per-segment backend behavior. A remote client can use a parameterized protected segment, or a parameter on an earlier segment, to make Envoy select an unprotected fallback while the backend resolves the protected resource. The relevant scope boundary is that the bypass requires both a path-based Envoy decision and a backend that strips semicolon parameters per segment. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.