chore(deps): update dependency ash_postgres to v2.15.2 [security] #636
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!636
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/hex-ash_postgres-vulnerability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.15.1→2.15.2AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows
CVE-2026-115627 / EEF-CVE-2026-115627 / GHSA-gr2r-f49c-9gm2
More information
Details
Summary
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_manyrelationship, or athroughrelationship, is loaded with a lateral join (for example with a per-record limit or sort),AshPostgres.DataLayerbuilds the query for the join resource, and for each resource along athroughpath, inlateral_join_query/3andthrough_step_queries/4without running that resource's read action, which is where attribute multitenancy is applied. When those resources usestrategy :attributemultitenancy, 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.
Impact
A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant's join rows.
Configurations
Reachable when the join resource of a
many_to_manyrelationship, or a resource along athroughpath, uses attribute multitenancy and holds rows from several tenants, and the relationship is loaded with a lateral join (for example with a limit, offset or sort on the relationship).Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by OSV.
AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
CVE-2026-115635 / EEF-CVE-2026-115635 / GHSA-36hg-wwp2-fg8w
More information
Details
Summary
Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant's record through a skipped upsert.
When
Ash.bulk_create/4or a single create runs as an upsert withreturn_skipped_upsert?: trueand the upsert is skipped (for example because itsupsert_conditiondoes not hold),AshPostgres.DataLayerreads the existing row back by the upsert identity indo_bulk_create/3andupsert/4. That lookup did not apply the resource's attribute multitenancy, so on a resource usingstrategy :attributeit could match and return the row of another tenant with the same identity values, exposing its fields to the caller.This issue affects ash_postgres: from 2.6.22 before 2.15.2.
Impact
A user of one tenant whose upsert is skipped receives another tenant's record with the same identity values.
Configurations
Reachable when a resource uses attribute multitenancy, an action performs upserts with
return_skipped_upsert?: true, and a caller can supply identity values that another tenant also uses.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by OSV.
Release Notes
ash-project/ash_postgres (ash_postgres)
v2.15.2Compare Source
Bug Fixes:
[security] apply attribute multitenancy when returning skipped upserts (CVE-2026-115635, GHSA-36hg-wwp2-fg8w) by Zach Daniel
[security] apply attribute multitenancy to the resources a lateral join passes through (CVE-2026-115627, GHSA-gr2r-f49c-9gm2) by Zach Daniel
ensure exists subqueries have the tenant by Zach Daniel
allow combining
DISTINCTandLOCKby Zach Danielensure identities are created after multitenancy attributes in migrations by Zach Daniel
always run atomic update query by Zach Daniel
properly support
parentreferences and limits onthroughjoins by Zach Danieldrop an unnamed custom index before recreating it under the same derived name (#901) by Johannes Welebil
properly set parent bindings temporal many to many by Zach Daniel
don't fully flatten array values by Zach Daniel
infer match: :simple for nullable match_tenant? references (#898) by Nelson Estevão
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
Pull request closed