cve.bz

CVE-2026-55736 ash-project ash

5.9 mediumEPSS 0.2%Fix available

Medium (5.9) in ash-project ash. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in ash 3.29.3.

On this page
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 that is intended to be controlled only by trusted server-side code. Action arguments declared with public?: false are meant to be set internally (for example via Ash.Changeset.set_private_argument/3) and must not be settable from end-user input. When a changeset is built from a parameter map, Ash filters out private arguments, but the filtering is incomplete. In the regular changeset path (for_create, for_update, for_destroy), private arguments are stripped only when the parameter key is an atom. When the key is a binary (string), as is the case for user-supplied parameters, the private argument is kept and the user controls its value. In the atomic path (Ash.Changeset.fully_atomic_changeset/4, also reached through atomic and bulk updates), private arguments are not stripped at all, regardless of whether the key is an atom or a binary. An attacker who can submit parameters to an action that defines a private argument can therefore inject a value for that argument. Depending on how the application uses the argument (for example an acting_user_id driving authorization or record ownership), this can lead to an integrity violation or privilege escalation. This issue affects ash: from 3.0.0 before 3.29.3.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-07-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash (Hex): fixed in 3.29.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-55736 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55736?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55736?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55736 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ashfrom 3.0.0 before 3.29.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-55736Hexash>=3.0.0 <3.29.33.29.3
EEF-CVE-2026-55736v3.29.2, v3.29.1, v3.29.0, v3.28.0, v3.27.8 and 249 moreno fix published
GHSA-f4hc-ppw9-4hhwHexash>=3.0.0 <3.29.33.29.3

References

Check your stackJSON