CVE-2026-69659 json
Memory exhaustion via unbounded deserialization of keyset pagination cursors in Ash.Page.Keyset
published 3mo ago modified 18d ago also EEF-CVE-2026-69659 , EUVD-2026-54937 , GHSA-j35q-v8h8-7mwq
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
Uncontrolled Resource Consumption vulnerability in ash-project ash allows an attacker to exhaust the memory of the node via a crafted keyset pagination cursor.
Read actions with keyset pagination deserialize the client-supplied page[:after] or page[:before] cursor in decode_values/2 in lib/ash/page/keyset.ex, which base64-decodes the value and passes it to :erlang.binary_to_term/2 without bounding its size. The Erlang external term format supports zlib-compressed payloads, which the decoder inflates transparently, so a cursor of a few kilobytes can allocate tens of megabytes of heap in a single call. Ash itself only ever encodes cursors uncompressed, so the decoder accepts a term shape its encoder never produces. Concurrent requests aggregate these allocations and can terminate the node.
This issue affects ash: from 1.17.0 before 3.31.1.
Patch / fix
- hex ash 3.31.1
- ash-project ash 3.31.1
Is CVE-2026-69659 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/ash-project/ash/security/advisories/GHSA-j35q-v8h8-7mwq referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | ash | >=1.17.0, <3.31.1 |
3.31.1 |
Affected products
- ash-project ash
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/ash-project/ash/commit/1816b103af975221210478d61db20adcea700319
patch
-
github.com
/ash-project/ash/security/advisories/GHSA-j35q-v8h8-7mwq
related, vendor-advisory, exploit, patch, advisory
-
osv.dev
/vulnerability/EEF-CVE-2026-69659
related, third-party-advisory, patch
-
cna.erlef.org
/cves/CVE-2026-69659.html
related, third-party-advisory, web
-
hex.pm
/packages/ash
package
Sources
- CVE List CVE-2026-69659
- NVD CVE-2026-69659
- OSV EEF-CVE-2026-69659
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.