CVE-2026-55518: Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation
(updated )
A critical missing authorization flaw exists in Avo’s association attach workflow. The UI and GET /resources/:resource/:id/:related/new path can check attach_<association>?, but the actual write endpoint, POST /resources/:resource/:id/:related, does not run the same authorization check before mutating the association.
As a result, an authenticated low-privileged Avo user can bypass hidden/disabled attach controls and directly attach related records to a parent record by sending a crafted POST request. In applications where associations represent teams, tenants, roles, projects, users, memberships, ownership, or other authorization-bearing relationships, this can lead to privilege escalation and cross-tenant data exposure.
References
- github.com/advisories/GHSA-8fq9-273g-6mrg
- github.com/avo-hq/avo/commit/995928e586fd1788dd496bd51c4dbe4a79cb2b9c
- github.com/avo-hq/avo/pull/4568
- github.com/avo-hq/avo/releases/tag/v3.32.1
- github.com/avo-hq/avo/security/advisories/GHSA-8fq9-273g-6mrg
- github.com/rubysec/ruby-advisory-db/blob/master/gems/avo/CVE-2026-55518.yml
- nvd.nist.gov/vuln/detail/CVE-2026-55518
- www.cve.org/CVERecord?id=CVE-2026-55518
Code Behaviors & Features
Detect and mitigate CVE-2026-55518 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →