Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-118657: 0.13% estimated exploitation activity in the next 30 days; percentile 2.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description `Context.Scheme()` unconditionally trusts four client-controlled HTTP headers to determine the request scheme, with no mechanism to configure trusted sources. This allows a remote unauthenticated attacker to bypass HTTPS redirect enforcement and suppress HSTS headers. The trusted headers (checked in this order of precedence): 1. `X-Forwarded-Proto` 2. `X-Forwarded-Protocol` 3. `X-Forwarded-Ssl` 4. `X-Url-Scheme`

Threat model Scenario A — Directly exposed application (vulnerable by default): The Echo application listens on HTTP and is reachable directly by clients (no L7 proxy in front), or an attacker can bypass the proxy and reach the backend directly. In this case, the attacker has full control over all request headers. Sending `X-Forwarded-Proto: https` defeats the `HTTPSRedirect` middleware entirely — traffic stays on plaintext HTTP, enabling man-in-the-middle attacks. This is the primary scenario. The application is vulnerable by default with no…

Published by the source

28 Oct 2026, 21:04 UTC

Last modified by the source

28 Oct 2026, 21:15 UTC

Source last checked

29 Oct 2026, 06:45 UTC

1. Revision 2 · amended · 29 Oct 2026

   Amended from osv record GHSA-2ffq-g2xg-c22p

2. Revision 1 · created · 28 Oct 2026

   Published from ghsa record GHSA-2ffq-g2xg-c22p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118657

Advisory: Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers
IDs: CVE-2026-118657, GHSA-2ffq-g2xg-c22p
Record: https://patchnext.com/advisories/cve-2026-118657 (revision 2, source checked 29 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/labstack/echo/v4 4.16.0; github.com/labstack/echo/v5 5.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/labstack/echo/v4: affected < 4.16.0; fixed in 4.16.0
- Go github.com/labstack/echo/v5: affected < 5.4.0; fixed in 5.4.0

## Suggested inspection (read-only)
- Go github.com/labstack/echo/v4: check the installed version with your package manager.
- Go github.com/labstack/echo/v5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/labstack/echo/v4, github.com/labstack/echo/v5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2ffq-g2xg-c22p (GitHub-reviewed advisory GHSA-2ffq-g2xg-c22p lists affected ranges: Go github.com/labstack/echo/v5 >=0 =0 <4.16.0)
- Verified: https://osv.dev/vulnerability/GHSA-2ffq-g2xg-c22p (OSV record GHSA-2ffq-g2xg-c22p lists affected ranges: Go github.com/labstack/echo/v5 >=0 =0 <4.16.0 (fixed))

Commands are suggestions: review each one before running it.