{
  "id": "CVE-2026-78699",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-78699",
  "published_at": "2026-08-30T15:13:23.875Z",
  "title": "rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres",
  "vendor": "ash-project",
  "product": "ash_postgres",
  "cvss": {
    "score": 7.2,
    "source": "cna",
    "vector": "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "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.\n\nAshPostgres.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.\n\nThis issue affects ash_postgres: from 0.25.0 before 2.13.0.",
  "cwe": "CWE-252",
  "cvss_by_source": {
    "cna": 7.2
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "ash-project",
        "product": "ash_postgres",
        "ranges": [
          "\u003e= 0.25.0, \u003c 2.13.0"
        ],
        "fixed_in": [
          "2.13.0"
        ]
      },
      {
        "vendor": "ash-project",
        "product": "ash_postgres",
        "ranges": [
          "\u003e= 03510dae24020e302558ef947be7ea874a9ce756, \u003c 8544ab15fe45784553c2d2da8ee1a388eee0174b"
        ],
        "fixed_in": [
          "8544ab15fe45784553c2d2da8ee1a388eee0174b"
        ]
      }
    ],
    "upgrade": [
      "Upgrade ash_postgres to 2.13.0 or later.",
      "Upgrade ash_postgres to 8544ab15fe45784553c2d2da8ee1a388eee0174b or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/ash-project/ash_postgres/security/advisories/GHSA-6fqq-j9c4-5766"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/ash-project/ash_postgres/commit/03510dae24020e302558ef947be7ea874a9ce756"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/ash-project/ash_postgres/commit/8544ab15fe45784553c2d2da8ee1a388eee0174b"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
