Home › Vulnerabilities

labstack Echo Go web framework Flaw CVE-2026-118264: Update Now

Published November 7, 2026 · Last updated November 7, 2026

CVE Critical Patch

The short version: CVE-2026-118264 is a critical-severity security flaw in labstack Echo Go web framework. The National Vulnerability Database (NVD) published it on October 28, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 7, 2026, CISA had not added CVE-2026-118264 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-118264

The record was filed by github.com. In its own words: "Echo is a Go web framework. From 4.0.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware selects a raw tunnel from a client WebSocket upgrade request before verifying that the configured upstream accepted the upgrade. If the upstream rejects the upgrade with an ordinary keep-alive response, later HTTP requests on the connection are sent directly to that upstream without passing through Echo's router or route-specific middleware. This can bypass authentication or authorization enforced only by Echo routes, but requires an accessible proxy route, a cooperating rejected-upgrade response, and a target without independent upstream authorization. This issue is fixed in 4.16.1 and 5.4.1."

Why Echo Go web framework admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-118264 9.1 (Critical) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Echo Go web framework running is none. Scoring string: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

Affected Echo Go web framework releases

According to the record, these releases are vulnerable:

  • version >= 4.0.0, < 4.16.1
  • version >= 5.0.0, < 5.4.1

The type of bug behind CVE-2026-118264

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-444, Inconsistent Interpretation of HTTP Requests. MITRE describes this class of bug as follows: "The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. (Roles: Common-Name, Attack-Focused, Common-Name, Attack-Focused)"
  • CWE-863, Incorrect Authorization. MITRE describes this class of bug as follows: "The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check."

Vendor remediation for CVE-2026-118264

The vendor advisory remediation for operators of Echo Go web framework, quoted for this page, is: "Upgrade labstack Echo v4 installs before 4.16.1 to 4.16.1 and Echo v5 installs before 5.4.1 to 5.4.1 (GitHub releases / commits 1855061 and 3fb0ba7). The Proxy middleware selected a raw X-Forwarded-For client IP that could bypass IP-based access controls; review reverse-proxy trust configuration after patching."

What to do about it

  • Update now: Upgrade labstack Echo v4 installs before 4.16.1 to 4.16.1 and Echo v5 installs before 5.4.1 to 5.4.1 (GitHub releases / commits 1855061 and 3fb0ba7). The Proxy middleware selected a raw X-Forwarded-For client IP that could bypass IP-based access controls; review reverse-proxy trust configuration after patching.
  • Who should act: IT teams, managed service providers, and developers who run or ship Echo Go web framework. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from labstack (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 28, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-118264. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-118264 record details from CISA and NVD

  • Attack complexity for CVE-2026-118264: low
  • CVE-2026-118264 attack requirements: present
  • Impact on connected systems: secrecy none, integrity none, availability none.
  • Who mapped the weakness type: the address listed on github.com (Secondary)
  • References in the NVD record: 5.
  • CISA SSVC decision points for CVE-2026-118264 (from NVD): exploitation=none; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • October 28, 2026: NVD publishes CVE-2026-118264.
  • November 7, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-118264 is not listed.
  • November 4, 2026: most recent NVD update (record status: Undergoing Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.