{
  "id": "CVE-2026-126083",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-126083",
  "published_at": "2026-11-10T21:09:33.682Z",
  "title": "Action Pack: Possible IP spoofing in Action Dispatch RemoteIp",
  "vendor": "rails",
  "product": "rails",
  "cvss": {
    "score": 7.4,
    "source": "cna",
    "vector": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "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.",
  "cwe": "CWE-348",
  "cvss_by_source": {
    "cna": 7.4
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "rails",
        "product": "rails",
        "ranges": [
          "\u003e= 8.1, \u003c 8.1.4.1"
        ],
        "fixed_in": [
          "8.1.4.1"
        ]
      }
    ],
    "upgrade": [
      "Upgrade rails to 8.1.4.1 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/rails/rails/security/advisories/GHSA-2gff-2mmg-m73p"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/rails/rails/commit/2a01a5ac521184419d9a92fa2c25e102e68cd227"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/rails/rails/releases/tag/v8.1.4.1"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
