{"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-118266 in the wild and no public exploit code.","fix":"Upgrade github.com/labstack/echo/v4 to 4.16.0 or later.","what":"CVE-2026-118266 is a medium-severity vulnerability in labstack echo, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118266 and fix it if it is affected.\n\nWhat it is: CVE-2026-118266 is a medium-severity vulnerability in labstack echo, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118266 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.16.0\n- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.16.0\n- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.0\n- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.0\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-118266/ (Markdown: https://insights.sbomify.com/CVE-2026-118266/index.md)","id":"CVE-2026-118266","markdown":"https://insights.sbomify.com/CVE-2026-118266/index.md","name":"CVE-2026-118266","record":{"aliases":["DEBIAN-CVE-2026-118266","ECHO-694f-e8ff-4ea6","GHSA-r7w9-592q-9vg4","UBUNTU-CVE-2026-118266"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","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: CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method","id":"CVE-2026-118266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"a2ui-project a2ui data-context Resolver data-context.ts resource consumption","id":"CVE-2026-118271"},"packages":[{"ecosystem":"Go","fixed":["4.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/labstack/echo/v4","purl":null,"source":"GHSA-r7w9-592q-9vg4"},{"ecosystem":"Go","fixed":["4.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/labstack/echo/v4","purl":"pkg:golang/github.com/labstack/echo/v4","source":"GHSA-r7w9-592q-9vg4"},{"ecosystem":"Go","fixed":["5.4.0"],"introduced":["5.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v5","purl":null,"source":"GHSA-r7w9-592q-9vg4"},{"ecosystem":"Go","fixed":["5.4.0"],"introduced":["5.0.0"],"last_affected":[],"package":"github.com/labstack/echo/v5","purl":"pkg:golang/github.com/labstack/echo/v5","source":"GHSA-r7w9-592q-9vg4"}],"prev":{"headline":"Echo: X-Real-IP extractor trusts the header value instead of the sending peer","id":"CVE-2026-118265"},"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-118266/"}