CVE-2026-118651

Echo: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Echo is a Go web framework. From 4.0.0 until 5.4.0, the Proxy middleware can preserve an attacker-supplied X-Real-IP header and forward it to an upstream service when Echo.IPExtractor is not configured. A remote client can therefore make upstream services receive a spoofed client address, undermining IP-based access controls, rate limiting, audit logging, or geographic restrictions that trust Echo's forwarded identity. This issue is fixed in Echo 5.4.0.

Analysis

AI-generated

Technical impact

The vulnerability in the Echo framework allows a remote client to supply an X‑Real‑IP header that is forwarded unchanged to upstream services when the IPExtractor is not configured. This flaw, mapped to CWE‑346 (Broken Access Control), lets an attacker masquerade as any client IP address, thereby bypassing IP‑based access controls, rate limiting, audit logging, and geographic restrictions that rely on the forwarded identity. The impact is a loss of confidentiality and integrity of access controls, as well as potential availability issues if upstream resources are exposed to unintended traffic.

Affected Systems

Labstack Echo web framework versions 4.0.0 through 5.4.0 are affected. The issue is resolved in Echo 5.4.0 and later releases. System administrators should identify any installations of Echo within that version range that allow unconfigured IP extraction.

Risk and Exploitability

The CVSS base score for this issue is 5.3, indicating moderate severity. The EPSS score of 0.00207 (less than 1%) indicates a very low exploitation probability, and the vulnerability is not listed in CISA’s KEV catalog. The attack vector is remote: an attacker sends an HTTP request containing a forged X‑Real‑IP header to the Echo application. No local privilege or authentication is required, so the threat is purely external and relies on the application trusting the header value.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Echo to version 5.4.0 or later, which removes the default forwarding of attacker‑supplied X‑Real‑IP headers
  • Configure Echo.IPExtractor to enforce strict header extraction rules, ensuring only legitimate client IPs are accepted
  • Verify that upstream services do not automatically trust X‑Real‑IP headers unless they have been validated by your own network controls

Generated by OpenCVE AI on November 6, 2026 at 02:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-99jh-6h7p-pp36 Echo: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Labstack
Labstack echo
Vendors & Products Labstack
Labstack echo
Type Values Removed Values Added
Description Echo is a Go web framework. From 4.0.0 until 5.4.0, the Proxy middleware can preserve an attacker-supplied X-Real-IP header and forward it to an upstream service when Echo.IPExtractor is not configured. A remote client can therefore make upstream services receive a spoofed client address, undermining IP-based access controls, rate limiting, audit logging, or geographic restrictions that trust Echo's forwarded identity. This issue is fixed in Echo 5.4.0.
Title Echo: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default
Weaknesses CWE-346
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-290

    Authentication Bypass by Spoofing

  • CWE-346

    Origin Validation Error

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 8:53 PM
Reserved
Oct 28, 2026, 5:25 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 8:17 PM
Modified
Oct 29, 2026, 9:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 7:30 PM