CVE-2026-78699

published 30 Aug 2026 · updated 19 Nov 2026

rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres

7.2HighCVSS 7.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.13.0 and 8544ab15fe45784553c2d2da8ee1a388eee0174b.

Unchecked Return Value vulnerability in ash-project ash_postgres allows a user who can drive a tenant rename to a name that collides with an existing tenant's schema to have their tenant record repointed at that other tenant's live schema, gaining access to its data. AshPostgres.MultiTenancy.rename_tenant/3 issues the ALTER SCHEMA ... RENAME TO ... with the non-raising Ecto.Adapters.SQL.query/2, discards its {:ok, _} | {:error, _} result, and unconditionally returns :ok. PostgreSQL rejects the rename when the target schema already exists (and on insufficient privilege or lock timeout), but that failure never reaches the caller. The calling manage_tenant update action therefore sees success and commits the tenant row with the new name, which is the schema of a different existing tenant, so subsequent reads and writes for that tenant run against the other tenant's data. This issue affects ash_postgres: from 0.25.0 before 2.13.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ash-project>=0.25.0 <2.13.0, >=03510dae24020e302558ef947be7ea874a9ce756 <8544ab15fe45784553c2d2da8ee1a388eee0174b2.13.0, 8544ab15fe45784553c2d2da8ee1a388eee0174b

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-78699 severity on Zeptric[![CVE-2026-78699](https://zeptric.io/badge/cve/CVE-2026-78699.svg)](https://zeptric.io/cve/CVE-2026-78699)