Vulnerability EEF-CVE-2026-64941

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
3 months ago
August 10, 2026 at 11:05 AM UTC
Open redirect in Phoenix.LiveView.validate_local_url!/2 via ASCII tab, LF and CR
0.5.0 - 0.6.0-dev and 0.6.0 - 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.1.0-rc.0 and 1.1.0-rc.1 and 1.1.0-rc.2 and 1.1.0-rc.3 and 1.1.0-rc.4 and 1.1.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0-rc.2 and 1.2.0-rc.3 and 1.2.0 - 1.2.8
0.5.0 - 0.6.0-dev and 0.6.0 - 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.1.0-rc.0 and 1.1.0-rc.1 and 1.1.0-rc.2 and 1.1.0-rc.3 and 1.1.0-rc.4 and 1.1.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0-rc.2 and 1.2.0-rc.3 and 1.2.0 - 1.2.8

Summary

Open redirect in Phoenix.LiveView.validate_local_url!/2 via ASCII tab, LF and CR

Details

Summary

URL Redirection to Untrusted Site ('Open Redirect') vulnerability in phoenixframework phoenix_live_view allows an attacker to send a victim's browser to an origin of the attacker's choosing via a :to value containing ASCII tab, LF or CR.

redirect/2 validates :to through the private validate_local_url!/2 in lib/phoenix_live_view.ex, which is intended to guarantee the target is a path within the application. It rejects a leading // and any backslash, but not ASCII tab, LF or CR. Browsers strip those three characters before parsing a URL, so a value such as /<TAB>/example.com passes validation as a path and is then resolved as the scheme-relative URL //example.com. The live navigation functions share the guard but are not affected, because the client expands their target against the current origin. push_patch/2 is also affected before 0.7.0, which is when that expansion was added.

This issue affects phoenix_live_view: from 0.5.0 before 1.0.19, from 1.1.0-rc.0 before 1.1.33, and from 1.2.0-rc.0 before 1.2.9.

Workarounds

Reject any untrusted value containing ASCII tab, LF or CR before passing it as :to to redirect/2, or to push_patch/2 before 0.7.0. Alternatively, map client-supplied navigation targets to a fixed set of known-good paths rather than forwarding the value.

Configurations

The application must pass an externally influenced value as :to to redirect/2, or to push_patch/2 before 0.7.0, for example a return_to parameter carried through sign-in or a navigation target taken from a handle_event/3 payload.

Impacted packages

Timeline

Published
3 months ago
August 10, 2026 at 11:05 AM UTC
Fixed (1.2.9)
3 months ago
August 10, 2026 at 09:42 AM UTC
Fixed (1.1.33)
3 months ago
August 10, 2026 at 09:43 AM UTC
Fixed (1.0.19)
3 months ago
August 10, 2026 at 09:45 AM UTC
Last Modified
1 day ago
November 20, 2026 at 05:23 PM UTC