https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 07 Nov 2026 15:08:31 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-115635 <p>Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant&#39;s record through a skipped upsert.</p> <p>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&#39;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.</p> <p>This issue affects ash_postgres: from 2.6.22 before 2.15.2.</p> <p>Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant&#39;s record through a skipped upsert.</p> <p>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&#39;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.</p> <p>This issue affects ash_postgres: from 2.6.22 before 2.15.2.</p> https://db.gcve.eu/vuln/fkie_cve-2026-115635