Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-115627Published 2026-10-25

CVE-2026-115627 — ash-project ash_postgres

medium (derived)

As of 2026-10-26, CVE-2026-115627 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in ash-project ash_postgres, CVSS v4.0 6, EPSS 0.2% (15.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-115627 as of 2026-10-26; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
6/10Medium (derived)
EPSS
0.2%Higher than 15.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.6/10Threadlinqs triage score
Published
Updated 2026-10-26
CVSS v4.0 6 (Medium, derived from score) · EPSS 0.2% (higher than 15.7% of all scored CVEs) · Priority 3.6/10 · Published 2026-10-25

Last updated:

What is CVE-2026-115627?

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.

The record classifies CVE-2026-115627 under weakness class CWE-863. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 25 days ago.

Severity and exploitation probability

CVSS v4.0 base score
6 — Medium (derived from score)
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 (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 15.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-25

Is CVE-2026-115627 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-115627

Patch reference: https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b. Vendor advisory: https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-115627

No threat campaign in the Threadlinqs corpus currently references CVE-2026-115627, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references