ash_postgres is vulnerable to Incorrect Authorization
60
CVE Score
Medium
Incorrect Authorization
With attribute multitenancy, AshPostgres reads an existing row by the upsert identity after an upsert is skipped. When return_skipped_upsert? is enabled and another tenant has matching identity values, the caller receives that tenant's record fields. The fix applies tenant scoping to the skipped-upsert result lookup.
Upgrade the ash_postgres library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and use attribute multitenancy with upserts that enable return_skipped_upsert?.
2.6.22 - 2.15.1
Fixed in 2.15.2ash_postgres is vulnerable to Incorrect Authorization in versions 2.6.22 - 2.15.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.