Incorrect Authorization vulnerability in ash-project ashpostgres allows a user to read another tenant's record through a skipped upsert.
CVE-2026-115635
Incorrect Authorization vulnerability in ash-project ashpostgres allows a user to read another tenant's record through a skipped upsert. When Ash.bulkcreate/4 or a single create runs as an upsert with returnskippedupsert?: true and the upsert is skipped (for example because its upsertcondition does not hold), AshPostgres.DataLayer reads the existing row back by the upsert identity in dobulkcreate/3 and upsert/4. That lookup did not apply the resource's attribute multitenancy, so on a resource using strategy :attribute it could match and return the row of another tenant with the same identity values, exposing its fields to the caller. This issue affects ashpostgres: from 2.6.22 before 2.15.2.
Assessment
- CVSS
- 6 (v4.0)
- Severity
- Medium
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 25 October 2026
- Last updated
- 26 October 2026
- Weakness
- CWE-863
- Assigner
- 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
At the source
References
- https://cna.erlef.org/cves/CVE-2026-115635.html
- https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w
- https://github.com/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9
- https://github.com/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5
- https://osv.dev/vulnerability/EEF-CVE-2026-115635
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-115635