Server-Side Request Forgery (SSRF) Affecting envoy-gateway package, versions <1.7.1-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.06% (18th 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 Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-ENVOYGATEWAY-15963353
  • published10 Apr 2026
  • disclosed6 Apr 2026

Introduced: 6 Apr 2026

CVE-2026-33540  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Chainguard envoy-gateway to version 1.7.1-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream envoy-gateway package and not the envoy-gateway package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, in pull-through cache mode, distribution discovers token auth endpoints by parsing WWW-Authenticate challenges returned by the configured upstream registry. The realm URL from a bearer challenge is used without validating that it matches the upstream registry host. As a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled realm URL. This vulnerability is fixed in 3.1.0.

CVSS Base Scores

version 3.1