Skip to main content
← All vulnerabilities
CVE-2026-118266GHSA-R7W9-592Q-9VG4EUVD-2026-112403

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.16.0, 5.4.0
None on Exploit-DB, Metasploit or GitHub

Summary

Echo, a Go web framework, has a flaw in its MethodOverride middleware that can cause CSRF protection to be skipped for state-changing POST requests when the middleware is registered before CSRF. As a result, an attacker could potentially make an authenticated victim's browser perform unintended actions on the affected application, though this requires a specific override configuration.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

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.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • labstack echo

    fixed in 4.16.0; From 5.0.0 · fixed in 5.4.0

  • github.com/labstack/echo/v5Go

    From 5.0.0 · fixed in 5.4.0

  • github.com/labstack/echo/v4Go

    fixed in 4.16.0

References 5

GitHub · labstack/echo