CVE-2026-78699Public exploit

Cross-tenant data access via ignored rename failure

Published Aug 30, 2026 · Updated Aug 30, 2026

Unchecked return handling in AshPostgres allows local users to read or write another tenant's data through a colliding schema rename. AshPostgres.MultiTenancy.rename_tenant/3 discards the non-raising SQL call's error and returns :ok, so the tenant update commits a name belonging to an existing schema. Exploitation requires schema-based multitenancy and a user-driven rename that permits a tenant name to collide with another tenant's schema.

CVSS severity7.2
High
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Unchecked return handling in AshPostgres allows local users to read or write another tenant's data through a colliding schema rename. AshPostgres.MultiTenancy.rename_tenant/3 discards the non-raising SQL call's error and returns :ok, so the tenant update commits a name belonging to an existing schema. Exploitation requires schema-based multitenancy and a user-driven rename that permits a tenant name to collide with another tenant's schema.

The record

CVE
CVE-2026-78699
Published
Aug 30, 2026
Updated
Aug 30, 2026
Vendor
Ash Framework
Product
AshPostgres
Classifications
CWE-252, CAPEC-1, T1213
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 30, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.25.0 <2.13.0
  2. Affected versionversion=03510dae24020e302558ef947be7ea874a9ce756 <8544ab15fe45784553c2d2da8ee1a388eee0174b

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Ash Framework · AshPostgresversion=0.25.0 <2.13.0; version=03510dae24020e302558ef947be7ea874a9ce756 <8544ab15fe45784553c2d2da8ee1a388eee0174b

Published CVSS scores

7.2Ash ProjectCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-252Unchecked Return Value
CAPEC-1Accessing Functionality Not Properly Constrained by ACLs
T1213Data from Information Repositories

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo