Read the docs

IP spoofing in Action Pack RemoteIp lets clients forge their address

Priority LOW 34CWE-348Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.0 · CNA. Fix status from CNA and GitHub.

Summary

Action Pack from 8.1.0.beta1 before 8.1.4.1 runs under Rack 3 and derives request.remote_ip from the Forwarded header, which is less trusted than X-Forwarded-For (CWE-348). When a reverse proxy passes a client-supplied Forwarded header through unchanged, an unauthenticated remote attacker can choose request.remote_ip. This can bypass IP-based access controls and rate limits and falsify client addresses in logs.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

Action Pack is a framework for handling and responding to web requests. From 8.1 until 8.1.4.1, 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. 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_for reads only X-Forwarded-For. Is served behind a proxy that does not remove or overwrite a client-supplied Forwarded header. Relies on request.remote_ip for 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. This issue is fixed in version 8.1.4.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00357 29th percentileScored 2026-11-16
Fix Fixed rails (rails): 8.1.4.1actionpack (RubyGems): 8.1.4.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Railsrails8.1 to before 8.1.4.18.1.4.1Patch availableCNA
—actionpack (RubyGems)8.1.0.beta1 to before 8.1.4.18.1.4.1Patch availableGHSA-2gff-2mmg-m73p
  • rails VendorRails Affected 8.1 to before 8.1.4.1 Fixed in 8.1.4.1 Patch available CNA
  • actionpack (RubyGems) Vendor— Affected 8.1.0.beta1 to before 8.1.4.1 Fixed in 8.1.4.1 Patch available GHSA-2gff-2mmg-m73p

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:*——Rails
  • cpe:2.3:a:rubyonrails:rails:*:*:*:*:*:*:*:* Versions — — ·Rails

Remediation

Upgrade Action Pack to 8.1.4.1, which fixes this issue for both rails and actionpack. The fix only detects a spoofed Forwarded header when the proxy also sets X-Forwarded-For, so configure the proxy to remove or overwrite client-supplied Forwarded headers.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

  • Fix · CNA rails (rails) Fixed in 8.1.4.1
  • Fix · GHSA-2gff-2mmg-m73p actionpack (RubyGems) Fixed in 8.1.4.1 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

Not affected: 2 products
  • Red Hat 3scale API Management Platform 2
  • Red Hat Satellite 6

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-126083
  2. 2026-11-10 Alias added: GHSA-2gff-2mmg-m73p
  3. 2026-11-10 Fix available: RubyGems/[email protected] · GHSA-2gff-2mmg-m73p
  4. 2026-11-10 CVSS score added · GHSA-2gff-2mmg-m73p
  5. 2026-11-10 Weakness changed · GHSA-2gff-2mmg-m73p
  6. 2026-11-10 5 new references · GHSA-2gff-2mmg-m73p
  7. 2026-11-11 Affected versions changed · Red Hat
  8. 2026-11-11 CVSS score added · Red Hat
  9. 2026-11-12 Priority changed: MEDIUM → LOW
  10. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2014-00124 Path traversal in Ruby on Rails lets remote attackers read files KEVCVSS 3.1HIGH 7.5
  • TI-2019-03828 File content disclosure in Rails Action View KEVCVSS 3.1HIGH 7.5
  • TI-2016-00672 Directory traversal in Rails Action View lets attackers read files KEVCVSS 3.1HIGH 7.5
  • TI-2019-03830 Command injection in Rails https://github.com/rails/rails CVSS 3.1CRITICAL 9.8
  • TI-2026-47043 Action Pack: Possible arbitrary file read and remote code execution in Active Storage variant processing CVSS 4.0CRITICAL 9.5
  • TI-2025-18040 Command injection in Rails activestorage CVSS 4.0CRITICAL 9.2
See all 185 →

Sources