ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-h53f-rm2w-w7rg

Echo: X-Real-IP extractor trusts the header value instead of the sending peer

Published Oct 23, 2026 · catalog updated Oct 23, 2026 · Echo: X-Real-IP extractor trusts

Last checked Oct 27, 2026, 12 days ago.

Open the advisory

Exploitation likelihood is not on this record for GHSA-h53f-rm2w-w7rg. A missing EPSS score is not a low risk. Compare Echo: X-Real-IP extractor trusts with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Echo: X-Real-IP extractor trusts).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
Go github.com/labstack/echo/v5

## Impact In Echo v5, checked whether the address supplied in belonged to a trusted range instead of checking the address of the direct network peer. An untrusted client could therefore supply a loopback or private address and have it returned by with the extractor's default trust options. Applications using this extractor for IP allowlists, IP-based rate limiting, audit logs or forwarding headers could accept a spoofed client identity. Exploitation requires that the attacker can reach Echo directly or that an intervening proxy passes through the attacker's value. Applications using the default direct IP extractor are unaffected. Echo v4 is unaffected by this v5 regression. ## Affected versions and patch All v5 releases from v5.0.0 through v5.4.0 are affected. Upgrade to [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1). The patch validates the direct peer before accepting a syntactically valid value, restoring the v4 trust model. [Fix commit](https://github.com/labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaaec). ## Workarounds Use until upgrading, or ensure that only trusted proxies can reach Echo and that they replace client-supplied forwarding headers. Configure trusted proxy ranges narrowly for the deployment. ## Credits Reported and patched by @rm-Umar. @Duodum independently reported the same issue in GHSA-c3r7-8j36-7mx8, which is tracked as a duplicate of this advisory.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/labstack/echo/v55.0.0 → 5.4.1

How to fix GHSA-h53f-rm2w-w7rg

  • Upgrade

    GHSA-h53f-rm2w-w7rg lists a fix boundary at 5.4.1. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in 5.0.0 → 5.4.1

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-h53f-rm2w-w7rg. A missing EPSS score is not a low risk. Compare Echo: X-Real-IP extractor trusts with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 5.0.0 → 5.4.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-348. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · Go Vulnerability Database

    Detected

    ## Impact In Echo v5, checked whether the address supplied in belonged to a trusted range instead of checking the address of the direct network peer. An untrusted client could therefore supply a loopback or private address and have it returned by with the extractor's default trust options. Applications using this extractor for IP allowlists, IP-based rate limiting, audit logs or forwarding headers

  2. Oct 23, 2026 · Go Vulnerability Database

    Fix available

    github.com/labstack/echo/v5 fixed in 5.4.1

  3. Oct 23, 2026 · Go Vulnerability Database

    Fix available

    github.com/labstack/echo/v5 fixed in 5.4.1

  4. Oct 23, 2026 · Go Vulnerability Database

    Updated

    ## Impact In Echo v5, checked whether the address supplied in belonged to a trusted range instead of checking the address of the direct network peer. An untrusted client could therefore supply a loopback or private address and have it returned by with the extractor's default trust options. Applications using this extractor for IP allowlists, IP-based rate limiting, audit logs or forwarding headers

Sources

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Go Vulnerability DatabaseOct 27, 2026