CVE-2026-126081 json
Action Pack: Possible Strong Parameters bypass in Parameters#each_key
published 8d ago modified yesterday also EUVD-2026-122932 , GHSA-wm3x-v3qw-4jh3
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository rails/rails. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
Action Pack is a framework for handling and responding to web requests. Prior to 8.1.4.1 and 8.0.5.2, 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. 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. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.
Patch / fix
- rubygems actionpack 8.0.5.2, 8.1.4.1
Is CVE-2026-126081 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | actionpack | >=8.1, <8.1.4.1 <8.0.5.2 |
8.1.4.1 8.0.5.2 |
Affected products
- rails rails
Classification
- Weakness
-
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
- Technology feeds
References
- github.com /rails/rails/commit/2fc8838300133931e19eed3ea6cee76a7e83f19c
- github.com /rails/rails/commit/8ba746e0a786458c281060823f2ccc5c5f6312ac
-
github.com
/rails/rails/security/advisories/GHSA-wm3x-v3qw-4jh3
advisory
- github.com /rails/rails/releases/tag/v8.0.5.2
- github.com /rails/rails/releases/tag/v8.1.4.1
Sources
- CVE List CVE-2026-126081
- NVD CVE-2026-126081
- Maintainer advisory GHSA-wm3x-v3qw-4jh3
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of rails/rails published their own advisory on GitHub. Reviewed sources take precedence over it.