https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 22:41:51 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-362328 EUVD-2026-362328 https://cve.radiocsirt.org/vuln/euvd-2026-362328 https://cve.radiocsirt.org/vuln/fkie_cve-2026-78699 <p>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&#39;s schema to have their tenant record repointed at that other tenant&#39;s live schema, gaining access to its data.</p> <p>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&#39;s data.</p> <p>This issue affects ash_postgres: from 0.25.0 before 2.13.0.</p> <p>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&#39;s schema to have their tenant record repointed at that other tenant&#39;s live schema, gaining access to its data.</p> <p>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&#39;s data.</p> <p>This issue affects ash_postgres: from 0.25.0 before 2.13.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-78699