Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3amended

Echo: BodyDump can discard BodyLimit overflow errors for unknown-length requests

CVE-2026-118263GHSA-x9ff-22gv-65f4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/labstack/echo/v5 5.4.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-118263: 0.39% estimated exploitation activity in the next 30 days; percentile 32.65 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Echo v5's BodyDump middleware captured a bounded prefix, drained the remaining request body while ignoring read errors, and then replaced the body with the captured prefix. With an outer BodyLimit, an unknown-length request such as an HTTP/1.1 chunked request, and a BodyDump capture limit below the BodyLimit threshold, an overflow detected during that drain could be discarded. The handler could consequently process a truncated request and return success even though the original body exceeded the configured limit. This is a conditional size-policy bypass; no general authentication bypass, production data modification or denial of service is claimed. Known-length requests rejected before BodyDump runs are unaffected by this path.

Affected versions and patch All v5 releases from v5.0.0 through v5.4.0 contain the affected drain-and-replace logic. Runtime reproduction confirmed v5.4.0; source comparison confirms the same request handling in v5.0.0. Upgrade to…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 6 · amended ·

    Amended from osv record GHSA-x9ff-22gv-65f4

  2. Revision 5 · amended ·

    Amended from ghsa record GHSA-x9ff-22gv-65f4

  3. Revision 4 · amended ·

    Amended from ghsa record GHSA-x9ff-22gv-65f4

  4. Revision 3 · amended ·

    Amended from ghsa record GHSA-x9ff-22gv-65f4

  5. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  6. Revision 1 · created ·

    Published from osv record GHSA-x9ff-22gv-65f4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118263

Advisory: Echo: BodyDump can discard BodyLimit overflow errors for unknown-length requests
IDs: CVE-2026-118263, GHSA-x9ff-22gv-65f4
Record: https://patchnext.com/advisories/ghsa-x9ff-22gv-65f4 (revision 6, source checked 29 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/labstack/echo/v5 5.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/labstack/echo/v5: affected >= 5.0.0, < 5.4.1; fixed in 5.4.1

## Suggested inspection (read-only)
- Go github.com/labstack/echo/v5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/labstack/echo/v5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x9ff-22gv-65f4 (OSV record GHSA-x9ff-22gv-65f4 lists affected ranges: Go github.com/labstack/echo/v5 >=5.0.0 <5.4.1 (fixed))
- Verified: https://github.com/advisories/GHSA-x9ff-22gv-65f4 (GitHub-reviewed advisory GHSA-x9ff-22gv-65f4 lists affected ranges: Go github.com/labstack/echo/v5 >=5.0.0 <5.4.1)

Commands are suggestions: review each one before running it.

Loading voting…