Skip to content
Connect AISign inSign up free
CVE-2026-786997.2HighCWE-252

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

ash-project · ash_postgres

Fixed in 2.13.0 · Affected: ash-project ash_postgres before 2.13.0 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days
5th percentile
050100

Higher than 5% of scored CVEs

7.2HighCVSS 4.0
LowHigh

DescriptionCVE.org

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 products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ash-project · ash_postgresfrom 0.25.0 before 2.13.0
  • ash-project · ash_postgresVersions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
August 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-78699 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References