Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Echo: CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method

CVSS 3.1 5.3 MEDIUMCheck source for fixed versionsKEV status unknown

Historical advisory recorded 3 Nov 2026 14:57:17 UTC. Read the latest advisory.

cve-program · CVE-2026-118266

Published

Echo is a Go web framework. Prior to 4.16.0 and 5.4.0, Echo's MethodOverride middleware accepts a safe HTTP method as the override target for a POST request. When MethodOverride is registered before CSRF in the post-routing middleware chain, route selection retains the original state-changing POST handler but the override changes the method before CSRF evaluates it, causing both token validation and Sec-Fetch-Site checks to be skipped. A cross-site exploit requires an authenticated victim and an override value that a browser-submitted request can control, such as the form getter used by the advisory reproducer; the default X-HTTP-Method-Override header getter is not settable by a cross-site form. This issue is fixed in 4.16.0 and 5.4.0.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-118266

Published

echo

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "labstack",
                    "product": "echo",
                    "versions": [
                        {
                            "version": "< 4.16.0",
                            "status": "affected"
                        },
                        {
                            "version": ">= 5.0.0, < 5.4.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 10:11 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current