Is CVE-2026-78699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-78699 being exploited in the wild.

How severe is CVE-2026-78699?

Informational severity, published 30 August 2026.

Which products and versions are affected?

Ash-Project Ash Postgres 0.25.0 to 2.12.x.

Is there a fix for CVE-2026-78699?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-78699 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-78699?

Check whether you run Ash-Project Ash Postgres at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-78699: ash-project ash_postgres tenant rename data exposure

CVE-2026-78699 · Severity: info · Published 2026-08-30

ash_postgres is an Elixir library that manages PostgreSQL databases in multi-tenant applications, where each tenant's data is isolated in a separate database schema. A flaw in the tenant rename function fails to check if the rename operation succeeds, allowing an attacker with tenant management privileges to redirect a tenant's schema pointer to another tenant's existing schema, gaining unauthorized access to their data.

Technologies: Ash-Project Ash Postgres. Vendors: Ash-Project.

Quick answers

Is CVE-2026-78699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-78699 being exploited in the wild.
How severe is CVE-2026-78699?: Informational severity, published 30 August 2026.
Which products and versions are affected?: Ash-Project Ash Postgres 0.25.0 to 2.12.x.
Is there a fix for CVE-2026-78699?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-78699 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-78699?: Check whether you run Ash-Project Ash Postgres at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an unchecked return value in the AshPostgres.MultiTenancy.rename_tenant/3 function. The function calls Ecto.Adapters.SQL.query/2 to execute ALTER SCHEMA ... RENAME TO ... but discards the result without checking for success or failure. When PostgreSQL rejects the rename (e.g., because the target schema name already exists), the error is never propagated to the caller, and the function unconditionally returns :ok. The calling code then commits the tenant record with the new schema name, causing that tenant's future database operations to run against the wrong (existing) schema, resulting in cross-tenant data access. This requires the attacker to have permissions to initiate a tenant rename operation. Versions 0.25.0 through 2.12.x are affected; the vulnerability was patched in 2.13.0.

Affected products

ash-project ash_postgres 0.25.0 to 2.12.x

Timeline

2026-08-30: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.