Action Pack: Possible Strong Parameters Bypass in Parameters#each_key
Published 12 Nov 2026 · Updated 12 Nov 2026
Is your project on an affected actionpack?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=8.1.0.beta1 <8.1.4.1
- Fixed in
- 8.1.4.1
bundle update --conservative actionpack # Gemfile: '>= 8.1.4.1'- Affected
- <8.0.5.2
- Fixed in
- 8.0.5.2
bundle update --conservative actionpack # Gemfile: '>= 8.0.5.2'Details
Impact
ActionController::Parameters#each_key delegates to the internal ActiveSupport::HashWithIndifferentAccess that holds the request parameters, so when called with a block it returns that hash instead of the Parameters instance. The hash does not respond to permitted?, so Active Model mass assignment (new, assign_attributes, update) accepts it without raising ActiveModel::ForbiddenAttributesError. An application that passes the return value of each_key to mass assignment could allow a remote, unauthenticated attacker to set attributes that the application does not permit, such as an authorization flag.
This is an incomplete fix of CVE-2020-8164, which made each, each_pair and each_value return the Parameters instance but left each_key delegated.
Details
The fixed releases define Parameters#each_key to yield each key and return the Parameters instance when given a block, as each, each_pair and each_value do, and to return an Enumerator without one. Code that used the return value of each_key as a hash now receives the Parameters instance, which mass assignment rejects unless it is permitted.
Affected applications
An application is affected if it passes the return value of ActionController::Parameters#each_key, called with a block, to mass assignment. Rails itself makes no such call.
Workarounds
Do not use the return value of each_key. Call it for its block only, and pass the permitted Parameters instance to mass assignment.
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/8ba746e0a786458c281060823f2ccc5c5f6312ac.patch
- 8.0: https://github.com/rails/rails/commit/2fc8838300133931e19eed3ea6cee76a7e83f19c.patch
Versions affected
- actionpack < 8.0.5.2
- actionpack >= 8.1, < 8.1.4.1
Credit
This issue was responsibly reported by HackerOne researcher smlee.
Is GHSA-wm3x-v3qw-4jh3 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected actionpack, and gives you the command that fixes it.
More advisories for actionpack
- MediumCVE-2026-126072Action Pack: Possible DoS vulnerability in Action Controller Live streaming · 12 Nov 2026
- MediumCVE-2026-126077Action Pack: Possible sensitive session information leak in Active Storage proxy mode · 12 Nov 2026
- MediumCVE-2026-126073Action Pack: Possible cache poisoning in Action Pack content negotiation · 10 Nov 2026
- LowCVE-2026-126067Action Pack: Missing SameSite attribute on session cookies from Action Pack session stores · 10 Nov 2026
- HighCVE-2026-126083Action Pack: Possible IP spoofing in Action Dispatch RemoteIp · 10 Nov 2026
- MediumCVE-2026-126076Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore · 10 Nov 2026
References
- Linkgithub.com/rails/rails/security/advisories/GHSA-wm3x-v3qw-4jh3
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-126081
- Linkgithub.com/rails/rails/commit/2fc8838300133931e19eed3ea6cee76a7e83f19c
- Linkgithub.com/rails/rails/commit/8ba746e0a786458c281060823f2ccc5c5f6312ac
- Packagegithub.com/rails/rails
- Linkgithub.com/rails/rails/releases/tag/v8.0.5.2
- Linkgithub.com/rails/rails/releases/tag/v8.1.4.1
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/GHSA-wm3x-v3qw-4jh3.yml
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.