{"answers":{"affected":"1 open source package ship an affected version, including ash_postgres.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78699 exists.","fix":"Upgrade ash_postgres to 2.13.0 or later.","what":"CVE-2026-78699 is a high-severity vulnerability in ash-project ash_postgres, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78699 and fix it if it is affected.\n\nWhat it is: CVE-2026-78699 is a high-severity vulnerability in ash-project ash_postgres, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78699 exists.\n\nAffected packages and fixed versions:\n- ash_postgres (Hex): affected from 0.25.0; fixed in 2.13.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-78699/ (Markdown: https://insights.sbomify.com/CVE-2026-78699/index.md)","id":"CVE-2026-78699","markdown":"https://insights.sbomify.com/CVE-2026-78699/index.md","name":"CVE-2026-78699","record":{"aliases":["EEF-CVE-2026-78699","GHSA-6fqq-j9c4-5766"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir Postgres library","requires_auth":"low_privilege","summary":"Attackers can rename tenants to collide with existing schemas, gaining unauthorized read and write access to other tenants' data due to unchecked return values.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":7.2,"severity":"high","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","version":"4.0"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"}],"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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres","id":"CVE-2026-78699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"389-ds-base: 389-ds-base: cve-2026-11610 incomplete fix may introduce a connection-stall dos","id":"CVE-2026-78701"},"packages":[{"ecosystem":"Hex","fixed":["2.13.0"],"introduced":["0.25.0"],"last_affected":[],"package":"ash_postgres","purl":"pkg:hex/ash_postgres","source":"EEF-CVE-2026-78699"}],"prev":{"headline":"Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names","id":"CVE-2026-78693"},"products":["ash_postgres"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["ash-project"]},"summary":"Attackers can rename tenants to collide with existing schemas, gaining unauthorized read and write access to other tenants' data due to unchecked return values.","url":"https://insights.sbomify.com/CVE-2026-78699/"}