chore(deps): update dependency ash_postgres to v2.15.2 [security] #636

Closed
renovate wants to merge 1 commit from renovate/hex-ash_postgres-vulnerability into main
Collaborator

This PR contains the following updates:

Package Type Update Change
ash_postgres (source) prod patch 2.15.1 → 2.15.2

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_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.

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_many relationship, or a resource along a through path, 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 Score: 6.0 / 10 (Medium)
  • Vector String: 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

References

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/4 or a single create runs as an upsert with return_skipped_upsert?: true and the upsert is skipped (for example because its upsert_condition does not hold), AshPostgres.DataLayer reads the existing row back by the upsert identity in do_bulk_create/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 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 Score: 6.0 / 10 (Medium)
  • Vector String: 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

References

This data is provided by OSV.


Release Notes

ash-project/ash_postgres (ash_postgres)

v2.15.2

Compare 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 DISTINCT and LOCK by Zach Daniel

  • ensure identities are created after multitenancy attributes in migrations by Zach Daniel

  • always run atomic update query by Zach Daniel

  • properly support parent references and limits on through joins by Zach Daniel

  • drop 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)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [ash_postgres](https://hex.pm/packages/ash_postgres) ([source](https://github.com/ash-project/ash_postgres)) | prod | patch | `2.15.1` → `2.15.2` | --- ### AshPostgres 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](https://nvd.nist.gov/vuln/detail/CVE-2026-115627) / EEF-CVE-2026-115627 / [GHSA-gr2r-f49c-9gm2](https://github.com/advisories/GHSA-gr2r-f49c-9gm2) <details> <summary>More information</summary> #### 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_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. ##### 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_many` relationship, or a resource along a `through` path, 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 Score: 6.0 / 10 (Medium) - Vector String: `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` #### References - [https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2](https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2) - [https://cna.erlef.org/cves/CVE-2026-115627.html](https://cna.erlef.org/cves/CVE-2026-115627.html) - [https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5](https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5) - [https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b](https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b) - [https://hex.pm/packages/ash_postgres](https://hex.pm/packages/ash_postgres) This data is provided by [OSV](https://osv.dev/vulnerability/EEF-CVE-2026-115627). </details> --- ### AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set [CVE-2026-115635](https://nvd.nist.gov/vuln/detail/CVE-2026-115635) / EEF-CVE-2026-115635 / [GHSA-36hg-wwp2-fg8w](https://github.com/advisories/GHSA-36hg-wwp2-fg8w) <details> <summary>More information</summary> #### 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/4` or a single create runs as an upsert with `return_skipped_upsert?: true` and the upsert is skipped (for example because its `upsert_condition` does not hold), `AshPostgres.DataLayer` reads the existing row back by the upsert identity in `do_bulk_create/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 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 Score: 6.0 / 10 (Medium) - Vector String: `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` #### References - [https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w](https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w) - [https://cna.erlef.org/cves/CVE-2026-115635.html](https://cna.erlef.org/cves/CVE-2026-115635.html) - [https://github.com/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5](https://github.com/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5) - [https://github.com/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9](https://github.com/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9) - [https://hex.pm/packages/ash_postgres](https://hex.pm/packages/ash_postgres) This data is provided by [OSV](https://osv.dev/vulnerability/EEF-CVE-2026-115635). </details> --- ### Release Notes <details> <summary>ash-project/ash_postgres (ash_postgres)</summary> ### [`v2.15.2`](https://github.com/ash-project/ash_postgres/blob/HEAD/CHANGELOG.md#v2152-2026-10-25) [Compare Source](https://github.com/ash-project/ash_postgres/compare/v2.15.1...v2.15.2) ##### Bug Fixes: - \[security] apply attribute multitenancy when returning skipped upserts ([CVE-2026-115635](https://cna.erlef.org/cves/CVE-2026-115635.html), [GHSA-36hg-wwp2-fg8w](https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w)) by Zach Daniel - \[security] apply attribute multitenancy to the resources a lateral join passes through ([CVE-2026-115627](https://cna.erlef.org/cves/CVE-2026-115627.html), [GHSA-gr2r-f49c-9gm2](https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2)) by Zach Daniel - ensure exists subqueries have the tenant by Zach Daniel - allow combining `DISTINCT` and `LOCK` by Zach Daniel - ensure identities are created after multitenancy attributes in migrations by Zach Daniel - always run atomic update query by Zach Daniel - properly support `parent` references and limits on `through` joins by Zach Daniel - drop an unnamed custom index before recreating it under the same derived name ([#&#8203;901](https://github.com/ash-project/ash_postgres/issues/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 ([#&#8203;898](https://github.com/ash-project/ash_postgres/issues/898)) by Nelson Estevão </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNjUuMiIsInVwZGF0ZWRJblZlciI6IjQzLjE2NS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0ZWQiLCJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSIsInNlY3VyaXR5Il19-->
chore(deps): update dependency ash_postgres to v2.15.2 [security]
All checks were successful
continuous-integration/drone/push Build is passing
cc7d69d98d
simon closed this pull request 2026-11-04 12:28:47 +01:00
Some checks are pending
continuous-integration/drone/push Build is passing
continuous-integration/drone/pr
Required

Pull request closed

Sign in to join this conversation.
No description provided.