CVE-2026-115635 json
AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
published 15d ago modified 14d ago also EEF-CVE-2026-115635 , EUVD-2026-109568 , GHSA-36hg-wwp2-fg8w
- cvss
- 6.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant's record through a skipped upsert.
When Ash.bulk_create/4 or a single create runs as an upsert with return_skipped_upsert?: true and the upsert is skipped (for example because its upsert_condition does not hold), AshPostgres.DataLayer reads the existing row back by the upsert identity in do_bulk_create/3 and upsert/4. That lookup did not apply the resource's attribute multitenancy, so on a resource using strategy :attribute it could match and return the row of another tenant with the same identity values, exposing its fields to the caller.
This issue affects ash_postgres: from 2.6.22 before 2.15.2.
Patch / fix
- hex ash_postgres 2.15.2
- ash-project ash_postgres 2.15.2
Is CVE-2026-115635 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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 14d ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | ash_postgres | >=2.6.22, <2.15.2 |
2.15.2 |
Affected products
- ash-project ash_postgres
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5
related, web
-
github.com
/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9
patch
-
github.com
/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-115635.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-115635
related
-
hex.pm
/packages/ash_postgres
package
Sources
- CVE List CVE-2026-115635
- NVD CVE-2026-115635
- OSV EEF-CVE-2026-115635
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.