Cross-site Scripting (XSS) Affecting ecs-service-connect-agent package, versions <0:v1.39.1.0-1.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-19821557
- published15 Sept 2026
- disclosed21 Sept 2026
Introduced: 15 Sep 2026
CVE-2026-73546 (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 /stats?format=html admin endpoint uses StatsHtmlRender, which sanitizes string statistic values but emits statistic names without HTML encoding. A data-plane component such as grpc_stats with stats_for_all_methods enabled can incorporate attacker-controlled path segments into cached dynamic statistic names. When an operator views the HTML stats page, the stored name can execute script with the admin interface's origin and issue privileged same-origin requests. The relevant scope boundary is that the admin interface must be browser-accessible and an enabled component must persist attacker-influenced text in statistic names. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-73546
- https://github.com/envoyproxy/envoy/commit/11d34660ca0322eb125d045a564d9d87f016397f
- https://github.com/envoyproxy/envoy/commit/884d30c56b835d5801733ae1dc38c94a08de23e8
- https://github.com/envoyproxy/envoy/commit/9484e17c34353662f9bfd30c74f61fa8c9ee7b83
- https://github.com/envoyproxy/envoy/commit/ab63a0e52b5a28472f2ff865b6464ae4004f7593
- https://github.com/envoyproxy/envoy/releases/tag/v1.36.10
- https://github.com/envoyproxy/envoy/releases/tag/v1.37.6
- https://github.com/envoyproxy/envoy/releases/tag/v1.38.4
- https://github.com/envoyproxy/envoy/releases/tag/v1.39.1
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-pv9h-4fxf-7vrg