Skip to content
Threat Brief

← All advisories

CVE-2026-115635

Medium 6.0No known exploitationFix available

AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set

Record last updated

CVSS score

6.0

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 16% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-863

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

VendorProductAffected versionsFixed inPer
ash-projectash_postgresfrom 2.6.22 before 2.15.22.15.2CVE Program
ash-projectash_postgresfrom af0903f1380468bbe1b61fe65acb33772b5e24a5 before 8aa81220c401cae412d21078d11b3519ea25d3a98aa81220c401cae412d21078d11b3519ea25d3a9CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references