{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "ash-project ash_postgres: all CVE events",
 "home_page_url": "https://patchwire.jonathanross.dev/products/ash-project--ash-postgres/",
 "feed_url": "https://patchwire.jonathanross.dev/feeds/products/ash-project--ash-postgres/all.json",
 "authors": [
  {
   "name": "Patchwire"
  }
 ],
 "language": "en",
 "items": [
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-115627/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-115627/",
   "title": "CVE-2026-115627 disclosed",
   "content_text": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant's join rows.\n\nWhen a many_to_many relationship, or a through relationship, is loaded with a lateral join (for example with a per-record limit or sort), AshPostgres.DataLayer builds the query for the join resource, and for each resource along a through path, in lateral_join_query/3 and through_step_queries/4 without running that resource's read action, which is where attribute multitenancy is applied. When those resources use strategy :attribute multitenancy, rows belonging to other tenants were joined, so the load returned destination records that the caller's tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2.",
   "date_published": "2026-10-25T19:49:50Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-115635/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-115635/",
   "title": "CVE-2026-115635 disclosed",
   "content_text": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant's record through a skipped upsert.\n\nWhen 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'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.\n\nThis issue affects ash_postgres: from 2.6.22 before 2.15.2.",
   "date_published": "2026-10-25T19:48:43Z"
  }
 ]
}