{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "source": "REFERENCES"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8544ab15fe45784553c2d2da8ee1a388eee0174b"
            }
          ],
          "repo": "https://github.com/ash-project/ash_postgres",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-6fqq-j9c4-5766"
  ],
  "database_specific": {
    "cna_assigner": "EEF",
    "cwe_ids": [
      "CWE-252"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/78xxx/CVE-2026-78699.json",
    "unresolved_ranges": [
      {
        "extracted_events": [
          {
            "introduced": "0.25.0"
          },
          {
            "fixed": "2.13.0"
          },
          {
            "introduced": "03510dae24020e302558ef947be7ea874a9ce756"
          },
          {
            "fixed": "8544ab15fe45784553c2d2da8ee1a388eee0174b"
          }
        ],
        "source": "AFFECTED_FIELD"
      },
      {
        "extracted_events": [
          {
            "introduced": "0.25.0"
          },
          {
            "fixed": "2.13.0"
          }
        ],
        "source": "CPE_FIELD"
      },
      {
        "extracted_events": [
          {
            "introduced": "0.25.0"
          },
          {
            "fixed": "2.13.0"
          }
        ],
        "source": "DESCRIPTION"
      }
    ]
  },
  "details": "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.",
  "id": "CVE-2026-78699",
  "modified": "2026-09-02T03:30:34.623259307Z",
  "published": "2026-08-30T15:13:23.875Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://cna.erlef.org/cves/CVE-2026-78699.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com"
    },
    {
      "type": "WEB",
      "url": "https://osv.dev/vulnerability/EEF-CVE-2026-78699"
    },
    {
      "type": "WEB",
      "url": "https://repo.hex.pm"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/78xxx/CVE-2026-78699.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/ash-project/ash_postgres/security/advisories/GHSA-6fqq-j9c4-5766"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-78699"
    },
    {
      "type": "FIX",
      "url": "https://github.com/ash-project/ash_postgres/commit/8544ab15fe45784553c2d2da8ee1a388eee0174b"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ash-project/ash_postgres"
    }
  ],
  "schema_version": "1.9.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres"
}