Quick answers
- Is CVE-2026-115627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115627 being exploited in the wild.
- How severe is CVE-2026-115627?
- Informational severity, published 25 October 2026.
- Which products and versions are affected?
- Ash-Project Ash Postgres 0.38.0 to before 2.15.2.
- Is there a fix for CVE-2026-115627?
- Yes: fixed in ash_postgres 2.15.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115627 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115627?
- Check whether you run Ash-Project Ash Postgres at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ash_postgres 2.15.2
Technical details
An incorrect authorization flaw in ash_postgres's lateral join handling (lateral_join_query/3 and through_step_queries/4) skips attribute-based multitenancy checks on intermediate resources in join paths. When relationships are loaded with lateral joins (per-record limit or sort), rows from other tenants are incorrectly joined, exposing destination records to unauthorized callers.
Affected products
- ash-project ash_postgres 0.38.0 to before 2.15.2
Timeline
- 2026-10-25: disclosed