CVE-2026-78699

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

AshPostgres.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.

This issue affects ash_postgres: from 0.25.0 before 2.13.0.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 30, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Aug 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 8544ab15fe45 (ash-project/ash_postgres)

Patch available: ash-project/ash_postgres v2.13.0 (contains commit 8544ab15fe45)

https://github.com/ash-project/ash_postgres/commit/8544ab15fe45784553c2d2da8ee1a388eee0174b
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-78699
generic

CVE-2026-78699

https://cna.erlef.org/cves/CVE-2026-78699.html
github Patch Available🟡 PoC Available

Unchecked error in `AshPostgres.MultiTenancy.rename_tenant/3` in AshPostgres commits a failed schema rename, allowing cross-tenant data exposure · Advisory · ash-project/ash_postgres · GitHub

https://github.com/ash-project/ash_postgres/security/advisories/GHSA-6fqq-j9c4-5766

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_postgres0.25.0 ... 2.9.1 (374 versions)2.13.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 04:27 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 04:05 UTCEG score recompute
  4. 2026-09-16 15:41 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:18 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 03:03 UTCEG score recompute
  11. 2026-09-13 02:44 UTCEG score recompute
  12. 2026-09-12 02:29 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:20 UTCEG score recompute
  16. 2026-09-10 14:05 UTCEG score recompute
  17. 2026-09-09 01:18 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 00:07 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 23:47 UTCEG score recompute
  22. 2026-09-04 23:30 UTCEG score recompute
  23. 2026-09-01 21:22 UTCEG score recompute
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 13:42 UTCEG score recompute
Show 7 more
  1. 2026-09-01 12:51 UTCEG score recompute
  2. 2026-09-01 04:52 UTCEG score recompute
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 16:21 UTCEG score recompute
  6. 2026-08-30 15:25 UTCEG score recompute
  7. 2026-08-30 15:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78699?
CVE-2026-78699 is a high vulnerability published on August 30, 2026. 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.…
When was CVE-2026-78699 disclosed?
CVE-2026-78699 was first published in the National Vulnerability Database on August 30, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78699 actively exploited?
CVE-2026-78699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-78699?
CVE-2026-78699 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-78699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78699

Explore →

Is Your Infrastructure Affected by CVE-2026-78699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs