{"items":[{"id":"NVI-00008993","kind":"vulnerability","title":"Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-cxf3-9h37-7rr8","CVE-2026-118264"],"plain_summary":"GitHub lists this reviewed advisory for github.com/labstack/echo/v4, github.com/labstack/echo/v5. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-109e0109f8141084ad8175fbe7496af8"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T20:17:05.900Z","value":"9.1 CRITICAL (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-650377f2625a085c33d74eb3fd44d41f"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.430%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37235. Missing scores are unknown.","source_id":"sr-109e0109f8141084ad8175fbe7496af8"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-64dedc18e6bd608bb3bc29091d21de8c","url":"https://github.com/advisories/GHSA-cxf3-9h37-7rr8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-cxf3-9h37-7rr8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-650377f2625a085c33d74eb3fd44d41f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118264","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-118264","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:59:08.616Z"},{"id":"sr-109e0109f8141084ad8175fbe7496af8","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118264","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.778Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v4","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 4.0.0, < 4.16.1"]},{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v5","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 5.0.0, < 5.4.1"]}],"null_published_at":"2026-11-07T07:07:42.479Z","source_updated_at":"2026-10-28T19:21:32.000Z","source_disclosed_at":"2026-10-23T20:49:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:56:36.327Z"},{"id":"NVI-00008993","kind":"vulnerability","title":"Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-cxf3-9h37-7rr8","CVE-2026-118264"],"plain_summary":"GitHub lists this reviewed advisory for github.com/labstack/echo/v4, github.com/labstack/echo/v5. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-109e0109f8141084ad8175fbe7496af8"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.430%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37235. Missing scores are unknown.","source_id":"sr-109e0109f8141084ad8175fbe7496af8"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-64dedc18e6bd608bb3bc29091d21de8c","url":"https://github.com/advisories/GHSA-cxf3-9h37-7rr8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-cxf3-9h37-7rr8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-109e0109f8141084ad8175fbe7496af8","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118264","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.778Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v4","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 4.0.0, < 4.16.1"]},{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v5","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 5.0.0, < 5.4.1"]}],"null_published_at":"2026-11-06T00:29:57.289Z","source_updated_at":"2026-10-28T19:21:32.000Z","source_disclosed_at":"2026-10-23T20:49:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:36.327Z"},{"id":"NVI-00008993","kind":"vulnerability","title":"Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-cxf3-9h37-7rr8","CVE-2026-118264"],"plain_summary":"GitHub lists this reviewed advisory for github.com/labstack/echo/v4, github.com/labstack/echo/v5. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-96e9b2bcb937fb66d45e87028110c536"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.430%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37215. Missing scores are unknown.","source_id":"sr-96e9b2bcb937fb66d45e87028110c536"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-64dedc18e6bd608bb3bc29091d21de8c","url":"https://github.com/advisories/GHSA-cxf3-9h37-7rr8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-cxf3-9h37-7rr8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-96e9b2bcb937fb66d45e87028110c536","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-118264","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.375Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v4","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 4.0.0, < 4.16.1"]},{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v5","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 5.0.0, < 5.4.1"]}],"null_published_at":"2026-11-04T02:53:03.152Z","source_updated_at":"2026-10-28T19:21:32.000Z","source_disclosed_at":"2026-10-23T20:49:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:56:36.327Z"},{"id":"NVI-00008993","kind":"vulnerability","title":"Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-cxf3-9h37-7rr8","CVE-2026-118264"],"plain_summary":"GitHub lists this reviewed advisory for github.com/labstack/echo/v4, github.com/labstack/echo/v5. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-64dedc18e6bd608bb3bc29091d21de8c","url":"https://github.com/advisories/GHSA-cxf3-9h37-7rr8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-cxf3-9h37-7rr8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v4","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 4.0.0, < 4.16.1"]},{"certainty":"source_listed","source_ids":["sr-64dedc18e6bd608bb3bc29091d21de8c"],"technology":"github.com/labstack/echo/v5","known_exclusions":[],"conditions_summary":"## Impact\n\nEcho's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware.\n\nThis can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication.\n\n## Affected versions and patch\n\nThe raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0.\n\nUpgrade to v4.16.1 or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1","public_affected_ranges":[">= 5.0.0, < 5.4.1"]}],"null_published_at":"2026-10-31T22:13:27.126Z","source_updated_at":"2026-10-28T19:21:32.000Z","source_disclosed_at":"2026-10-23T20:49:37.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:56:36.327Z"}],"next_cursor":null,"snapshot_revision":"42594"}