{"answers":{"affected":"4 open source packages ship an affected version, including github.com/labstack/echo/v4 and github.com/labstack/echo/v5.","exploited":"There is no known exploitation of CVE-2026-118264 in the wild and no public exploit code.","fix":"Upgrade github.com/labstack/echo/v4 to 4.16.1 or later.","what":"CVE-2026-118264 is a critical vulnerability in labstack echo, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118264 and fix it if it is affected.\n\nWhat it is: CVE-2026-118264 is a critical vulnerability in labstack echo, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118264 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/labstack/echo/v4 (Go): affected from 4.0.0; fixed in 4.16.1\n- github.com/labstack/echo/v4 (Go): affected from 4.0.0; fixed in 4.16.1\n- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.1\n- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-118264/ (Markdown: https://insights.sbomify.com/CVE-2026-118264/index.md)","id":"CVE-2026-118264","markdown":"https://insights.sbomify.com/CVE-2026-118264/index.md","name":"CVE-2026-118264","record":{"aliases":["DEBIAN-CVE-2026-118264","ECHO-e1b6-15b1-4b64","GHSA-cxf3-9h37-7rr8","ROOT-APP-GOBINARY-GHSA-cxf3-9h37-7rr8","UBUNTU-CVE-2026-118264"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls","id":"CVE-2026-118264","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Echo: X-Real-IP extractor trusts the header value instead of the sending peer","id":"CVE-2026-118265"},"packages":[{"ecosystem":"Go","fixed":["4.16.1"],"introduced":["4.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v4","purl":null,"source":"GHSA-cxf3-9h37-7rr8"},{"ecosystem":"Go","fixed":["4.16.1"],"introduced":["4.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v4","purl":"pkg:golang/github.com/labstack/echo/v4","source":"GHSA-cxf3-9h37-7rr8"},{"ecosystem":"Go","fixed":["5.4.1"],"introduced":["5.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v5","purl":null,"source":"GHSA-cxf3-9h37-7rr8"},{"ecosystem":"Go","fixed":["5.4.1"],"introduced":["5.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v5","purl":"pkg:golang/github.com/labstack/echo/v5","source":"GHSA-cxf3-9h37-7rr8"}],"prev":{"headline":"Echo: BodyDump can discard BodyLimit overflow errors for unknown-length requests","id":"CVE-2026-118263"},"products":["echo"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["labstack"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-118264/"}