cve.bz

CVE-2026-115627 ash-project ash postgres: Incorrect Authorization

6.0 mediumEPSS 0.2%Fix available

Medium (6.0) in ash-project ash postgres. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in ash_postgres 2.15.2.

On this page
Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant's join rows. When a many_to_many relationship, or a through relationship, is loaded with a lateral join (for example with a per-record limit or sort), AshPostgres.DataLayer builds the query for the join resource, and for each resource along a through path, in lateral_join_query/3 and through_step_queries/4 without running that resource's read action, which is where attribute multitenancy is applied. When those resources use strategy :attribute multitenancy, rows belonging to other tenants were joined, so the load returned destination records that the caller's tenant is not related to. This issue affects ash_postgres: from 0.38.0 before 2.15.2.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • ash_postgres (Hex): fixed in 2.15.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-115627 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115627?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115627?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115627 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ash-project ash_postgresfrom 0.38.0 before 2.15.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-115627Hexash_postgres>=0.38.0 <2.15.22.15.2
EEF-CVE-2026-115627v2.15.1, v2.15.0, v2.14.5, v2.14.4, v2.14.3 and 314 moreno fix published

References

Check your stackJSON