open-redirect

Block open redirects in login flows by validating redirect targets against a trusted host allowlist and rejecting unsafe inputs. Redirecting unvalidated return-to parameters to a safe default prevents attackers from sending users to malicious sites during authentication.

An open redirect vulnerability allows attackers to redirect users from trusted domains to malicious sites. In OAuth callbacks, validating redirect targets against a host allowlist prevents credential theft and phishing by ensuring callers cannot dictate unsafe navigation paths.

Validate redirect URLs by enforcing a host allowlist and explicitly blocking scheme-relative URLs. Applying a safe_redirect validator to user-input-driven redirects ensures that untrusted targets are rejected and replaced with a safe default destination.

You can use a redirect validator for any user-input-driven redirects, not just authentication. It applies to OAuth callbacks and all navigation features, enforcing a host allowlist and blocking risky patterns to ensure safe navigation across the entire web application.

Your web app redirects to untrusted domains because return-to parameters lack validation against a host allowlist. Blocking scheme-relative URLs and redirecting to a safe default on validation failure prevents this open redirect vulnerability.