Homepage

Use of Non-Canonical URL Paths for Authorization Decisions 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.53% (43rd 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-19820865
  • published15 Sept 2026
  • disclosed21 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 15 Sep 2026

CVE-2026-73551  (opens in a new tab)
CWE-647  (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's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.