CVE-2026-93477
Medium 5.9No known exploitationFix availablePrivate action arguments can be set by user input on the bulk destroy and bulk update paths in Ash
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 10% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in ash-project ash allows a user to set the value of a private action argument on the bulk destroy and bulk update paths. Action arguments declared with public?: false are meant to be set only by trusted server-side code (for example via Ash.Changeset.set_private_argument/3) and must not be settable from end-user input. CVE-2026-55736 fixed the non-bulk changeset path to strip private arguments from user-supplied parameter maps, but the bulk destroy and bulk update paths were not covered. Ash.Actions.Destroy.Bulk.base_changeset/5 and Ash.Actions.Update.Bulk.base_changeset/5 match every key in the caller-supplied parameter map against all of the action's arguments with no public? check, then apply the matches to the base changeset. A caller who can submit parameters to a bulk destroy or bulk update action (for example through AshJsonApi, AshGraphql, or a controller that forwards request parameters to Ash.bulk_destroy/4 or Ash.bulk_update/4) can therefore set any private argument of that action, including one referenced by an arg(...) template in the action's changes or validations. Depending on how the application uses the argument (for example an acting_user_id driving authorization or record ownership, or audit metadata), this can lead to an integrity violation or privilege escalation. The fix requires public? in the argument matching on both bulk paths; private arguments remain settable server-side via the :private_arguments option. This issue affects ash: from 2.17.15 before 3.33.11.
Weakness: CWE-915
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| ash-project | ash | from 2.17.15 before 3.33.11 | 3.33.11 | CVE Program |
| ash-project | ash | from 8c17434803b2e91de522bdfbd0ca918e5d5898df before 6b7ac53a0a2532291eb940d7beaf0fbb2da6fc4f | 6b7ac53a0a2532291eb940d7beaf0fbb2da6fc4f | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 6b7ac53 in ash-project/ash (opens in a new tab)patch
- GHSA-c2p4-p7q6-hr2j (opens in a new tab)vendor-advisory
- EEF CNA record for CVE-2026-93477 (opens in a new tab)related
- Introducing commit 8c17434 in ash-project/ash (opens in a new tab)related
- OSV record EEF-CVE-2026-93477 (opens in a new tab)related