CVE-2026-118657

{"id": "CVE-2026-118657", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.2, "exploitabilityScore": 1.6}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "labstack", "product": "echo", "versions": [{"status": "affected", "version": ">= 5.0.0, < 5.4.0"}, {"status": "affected", "version": "< 4.16.0"}]}]}], "published": "2026-10-28T21:16:55.693", "references": [{"url": "https://github.com/labstack/echo/commit/b838391e2eade87ae7e5a09d7bb5087bec271ec1", "source": "security-advisories@github.com"}, {"url": "https://github.com/labstack/echo/commit/fc410094b2f3415cf2bf5204082137b205bfd5af", "source": "security-advisories@github.com"}, {"url": "https://github.com/labstack/echo/releases/tag/v4.16.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/labstack/echo/releases/tag/v5.4.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/labstack/echo/security/advisories/GHSA-2ffq-g2xg-c22p", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-346"}]}], "descriptions": [{"lang": "en", "value": "Echo is a Go web framework. Prior to 4.16.0 and 5.4.0, Context.Scheme unconditionally trusts forwarded scheme headers from any client. A client that reaches Echo directly over plaintext HTTP can claim an HTTPS scheme and bypass HTTPSRedirect because the request is treated as already secure. Separately, behind a TLS-terminating proxy that passes an attacker-controlled header, a claimed HTTP scheme can suppress the Strict-Transport-Security header even though the browser receives the response over HTTPS. The practical risk is reduced when a trusted proxy overwrites the headers and direct backend access is prevented, but the framework previously had no trusted-source configuration for this decision. This issue is fixed in 4.16.0 and 5.4.0."}], "lastModified": "2026-10-29T15:15:16.507", "sourceIdentifier": "security-advisories@github.com"}