NULL Pointer Dereference 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-19820168
- published15 Sept 2026
- disclosed21 Sept 2026
Introduced: 15 Sep 2026
CVE-2026-48521 (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 ProdClusterManagerFactory::allocateConnPool dereferences transport_socket_options while selecting an HTTP/3 connection pool without first checking whether the pointer is null. LoadBalancerContext implementations used by synthetic, mirror, health-check, and async-client calls can return no transport-socket options. With auto_config and HTTP/3 enabled, routine traffic reaching one of those contexts can crash an Envoy worker. The relevant scope boundary is that the affected branch requires HTTP/3 in the protocol set and a context that supplies no transport-socket options. 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-48521
- https://github.com/envoyproxy/envoy/commit/8ef2da8527fcd17388b046c1add4fb47fb5d0868
- https://github.com/envoyproxy/envoy/commit/cec4899acf03cf551f28611a5f32385648d95f96
- https://github.com/envoyproxy/envoy/commit/e7b4839beef7f43594ce8e94c4563c80db04a8a7
- https://github.com/envoyproxy/envoy/commit/f5436f44103fb14cb8ba42a8db0f54a06c98c45a
- 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-5vff-j9p4-38j3