CVE-2026-126083: Action Pack: Possible IP spoofing in Action Dispatch RemoteIp
Impact Since Rails 8.1.0, ActionDispatch::RemoteIp derives request.remoteip from Rack::Request#forwardedfor, which under Rack 3 reads the RFC 7239 Forwarded header in preference to X-Forwarded-For. When a reverse proxy appends the client address to X-Forwarded-For but passes a client-supplied Forwarded header through unchanged, request.remoteip returns an address chosen by the client, and the IP spoofing check does…
Published Nov 10, 2026
Affected packages
actionpack
- Ecosystem
- RubyGems
- Affected
- >= 8.1.0.beta1, < 8.1.4.1
- Fixed in
- 8.1.4.1
- Check
bundle info actionpack
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Since Rails 8.1.0, ActionDispatch::RemoteIp derives request.remote_ip from Rack::Request#forwarded_for, which under Rack 3 reads the RFC 7239 Forwarded header in preference to X-Forwarded-For. When a reverse proxy appends the client address to X-Forwarded-For but passes a client-supplied Forwarded header through unchanged, request.remote_ip returns an address chosen by the client, and the IP spoofing check does not raise, because it compares only Client-Ip with the forwarded addresses. An unauthenticated attacker could therefore spoof request.remote_ip, possibly bypassing IP-based access controls and rate limits keyed on the client address (including the default by: of rate_limit), and falsifying the client address in logs.
Details
The 8.1.0 change (2d084af8) switched ActionDispatch::RemoteIp from reading X-Forwarded-For directly to Rack's forwarded_for, in order to reuse Rack's port handling. Rails continues to honor Forwarded, the standard header.
In the fixed releases, when config.action_dispatch.ip_spoofing_check is enabled (the default), ActionDispatch::RemoteIp also compares the first untrusted client address in Forwarded with the first untrusted client address in X-Forwarded-For, as exact strings, and raises ActionDispatch::RemoteIp::IpSpoofAttackError when both headers are present and the addresses differ. Deployments whose proxies report the client address inconsistently between the two headers will receive this error after upgrading. See the actionpack CHANGELOG.
Affected applications
An application is affected if it meets all of these requirements:
- Runs Rails 8.1.0 through 8.1.4 with Rack 3. Under Rack 2.2,
forwarded_forreads onlyX-Forwarded-For. - Is served behind a proxy that does not remove or overwrite a client-supplied
Forwardedheader. - Relies on
request.remote_ipfor access control, rate limiting, or auditing.
The fix detects a spoofed Forwarded header only when the proxy also sets X-Forwarded-For. An application whose proxy passes a client-supplied Forwarded header through and sets no X-Forwarded-For remains exposed after upgrading, and should configure the proxy to remove or overwrite Forwarded, or apply the workaround below.
Mitigation
- Upgrade to a fixed version of
actionpack. - Configure reverse proxies to remove or overwrite any client-supplied
Forwardedheader.
Workarounds
Applications whose proxies set X-Forwarded-For can make Rack ignore the Forwarded header, restoring the client address resolution of Rails 8.0, by setting Rack::Request.forwarded_priority = [:x_forwarded] in an initializer. This setting is available in Rack 3.0.0 and later, and it also causes Rack to ignore Forwarded when determining the request scheme, host, and port.
Releases
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
- 8.1: https://github.com/rails/rails/commit/2a01a5ac521184419d9a92fa2c25e102e68cd227.patch
Versions affected
- actionpack >= 8.1, < 8.1.4.1
Credit
This issue was responsibly reported by HackerOne researcher luryus.
References
- https://github.com/rails/rails/security/advisories/GHSA-2gff-2mmg-m73p
- https://github.com/rails/rails/commit/2a01a5ac521184419d9a92fa2c25e102e68cd227
- https://github.com/rails/rails/releases/tag/v8.1.4.1
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/GHSA-2gff-2mmg-m73p.yml
- https://github.com/advisories/GHSA-2gff-2mmg-m73p
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-126072
Action Pack: Possible DoS vulnerability in Action Controller Live streaming
medium5.9Nov 12, 2026CVE-2026-126077
Action Pack: Possible sensitive session information leak in Active Storage proxy mode
medium6.8Nov 12, 2026CVE-2026-126081
Action Pack: Possible Strong Parameters Bypass in Parameters#each_key
high7.5Nov 12, 2026CVE-2026-126067
Action Pack: Missing SameSite attribute on session cookies from Action Pack session stores
low3.1Nov 10, 2026CVE-2026-126073
Action Pack: Possible cache poisoning in Action Pack content negotiation
medium4.8Nov 10, 2026CVE-2026-126076
Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore
medium4.2Nov 10, 2026
