GHSA-2j8w-xcrc-x985: Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835

Published Nov 9, 2026
·
Updated

Rack is a modular Ruby web server interface. From 3.0 until 3.1.23 and 3.2.8, Rack::Request#hostwithport, #baseurl, and #url can return an attacker-controlled invalid authority from Host, X-Forwarded-Host, or Forwarded: host= verbatim. Applications without an independent host allowlist that use these methods for absolute URLs, redirects, or origin-dependent checks can emit attacker-chosen delimiters, enabling redirect manipulation, string-based allowlist bypass, or unescaped markup reflection. Rails overrides these methods and is not expected to be affected. This issue is fixed in versions 3.1.23 and 3.2.8.

Affected Software

1 affected component
rubygems/rack>=3.0<3.1.23, >=3.2<3.2.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 3.1.23
  2. Upgrade

    Upgrade Rack to a version that resolves this vulnerability.

    Fixed in 3.2.8

Event History

Nov 9, 2026
CVE Published
via OSV·09:57 PM
Data Sourced
via OSV·09:57 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are most exposed?

Applications that do not independently allowlist hosts and use Rack request URL helpers to construct absolute URLs, redirects, or origin-dependent checks are most exposed. Rails overrides these methods and is not expected to be affected.

2

What request headers can supply the attacker-controlled value?

The value can come from the Host header, X-Forwarded-Host header, or the host parameter in a Forwarded header. The affected methods can return an invalid authority from these inputs verbatim.

3

How can I determine whether my application needs remediation?

Check whether the application uses Rack 3.0 through versions before 3.1.23 or 3.2.8, and whether it calls host_with_port, base_url, or url. Prioritize cases where those values are used without an independent host allowlist.

4

What can be done if an upgrade is not immediately possible?

Apply an independent host allowlist before using request-derived host values for URL generation, redirects, or origin checks. This reduces exposure to attacker-controlled invalid authorities.

5

Which versions contain the fix?

The issue is fixed in Rack 3.1.23 and 3.2.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203