VYPR
Medium severityGHSA Advisory· Published May 8, 2026

Devise has an Open Redirect via Unvalidated `request.referrer` in Timeoutable Session Timeout Handler

CVE-2026-40295

Description

Summary

When the Timeoutable module is enabled in Devise, the FailureApp#redirect_url method returns request.referrer — the HTTP Referer header, which is attacker-controllable — without validation for any non-GET request that results in a session timeout. An attacker who hosts a page with an auto-submitting cross-origin form can cause a victim with an expired Devise session to be redirected to an arbitrary external URL. This contrasts with the GET timeout path (which uses server-side attempted_path) and Devise's own store_location_for mechanism (which strips external hosts via extract_path_from_location), both of which are protected; only the non-GET timeout redirect path is unprotected.

Details

The vulnerable code is in lib/devise/failure_app.rb:

def redirect_url
  if warden_message == :timeout
    flash[:timedout] = true if is_flashing_format?

    path = if request.get?
      attempted_path          # safe: server-side value from warden options
    else
      request.referrer        # UNSAFE: HTTP Referer header, attacker-controlled
    end

    path || scope_url
  else
    scope_url
  end
end

This is passed directly to redirect_to:

def redirect
  store_location!
  # ...
  redirect_to redirect_url   # redirect_url may be an external attacker URL
end

The GET timeout path uses attempted_path, which is set server-side by Warden and cannot be influenced by the client. The store_location! method also only runs for GET requests, so no session-based protection is applied on POST timeouts.

By contrast, Devise's store_location_for method (used elsewhere) correctly sanitizes URLs via extract_path_from_location, which strips the scheme and host.

Impact

  • Victims with expired sessions who click any attacker-crafted link or visit an attacker page with an auto-submitting form are redirected to an arbitrary external URL.
  • The redirect happens transparently via a trusted domain (the target app's domain), bypassing browser phishing warnings.
  • An attacker can redirect victims to a fake login page to harvest credentials (phishing), or to malicious download sites.

_Note_: Rails' built-in open-redirect protection does not mitigate this issue. Devise::FailureApp is an ActionController::Metal app with its own isolated copy of the relevant redirect configuration, so config.action_controller.action_on_open_redirect = :raise (and the older raise_on_open_redirects setting) do not reach it.

Patches

This is patched in Devise v5.0.4. Users should upgrade as soon as possible.

Workaround

None beyond upgrading. If an upgrade is not immediately possible, the same changes from the patch commit can be applied as a monkey-patch in a Rails initializer (Devise::FailureApp#redirect_url and Devise::Controllers::StoreLocation#extract_path_from_location). Remove the monkey-patch after upgrading.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Devise's Timeoutable module redirects non-GET timeout requests to the unvalidated HTTP Referer header, enabling open redirect phishing attacks.

Vulnerability

Overview

CVE-2026-40295 is an open redirect vulnerability in the Devise authentication library Devise for Ruby on Rails [1]. When the Timeoutable module is enabled, rememberable or any module that can cause a session timeout is enabled, the FailureApp#redirect_url method returns request.referrer (the HTTP Referer header, attacker-controllable) without validation for any non-GET request that results in a session timeout. This differs from the GET timeout path, which uses the server-side attempted_path and is safe. The GET path also uses store_location!, which runs and protects with extract_path_from_location that strips scheme and host [2].

Exploitation

An attacker hosts a page with an auto-submitting cross-origin form. When a victim with an expired Devise session visits that page, the referrer is sent along with the POST request, and the server. The Devise server detects the timeout and redirect the victim to the attacker-controlled URL, bypassing browser phishing warnings because the redirect originates from a trusted domain [2]. The attack requires the victim to have the session timeout and the application to configuration redirect_on_timeout: true or similar behavior [2].

Impact

An attacker can redirect victims to a fake login pages to harvest credentials, perform phishing, leading to phishing and credential theft. The impact is heightened because the redirect appears to come from the trusted application domain, making phishing detection difficult [2].

Mitigation

The Devise maintainers have implemented a fix by adding validation to the redirect_url method to reject external URLs when the referrer appearset. The fix is incorporated in subsequent to GitHub security advisory GHSA-jp94-3292-c3xv and patched in Devise versions ≥4.10.0 (pending). Users should update to the latest version [2].

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
deviseRubyGems
< 5.0.45.0.4

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

3