CVE-2026-55518: CWE-639: Authorization Bypass Through User-Controlled Key in avo-hq avo
Avo is a framework to create admin panels for Ruby on Rails apps. Prior to 3.32.1 and 4.0.0.beta.51, Avo's association attach workflow checks attach_<association>? in the UI and GET /resources/:resource/:id/:related/new path, but the actual write endpoint, POST /resources/:resource/:id/:related, does not run the same authorization check before mutating the association through Avo::AssociationsController#create. An authenticated low-privileged Avo user can bypass hidden or disabled attach controls and directly attach related records to a parent record by sending a crafted POST request, which can lead to privilege escalation and cross-tenant data exposure where associations represent authorization-bearing relationships. This issue is fixed in versions 3.32.1 and 4.0.0.beta.51.
AI Analysis
Technical Summary
CVE-2026-55518 is an authorization bypass vulnerability in the avo-hq Avo framework for Ruby on Rails admin panels. The flaw arises because the POST endpoint /resources/:resource/:id/:related used to attach associations does not enforce the same authorization checks as the UI and GET endpoints. This allows an authenticated user with low privileges to craft POST requests to attach related records directly, bypassing UI restrictions. Such unauthorized association mutations can lead to privilege escalation and cross-tenant data exposure when associations represent authorization boundaries. The vulnerability affects versions prior to 3.32.1 and 4.0.0.beta.51 and is fixed in those versions.
Potential Impact
An authenticated low-privileged user can bypass intended authorization controls to attach related records to parent records. This can result in privilege escalation and unauthorized cross-tenant data exposure where associations control access. The vulnerability has a high impact on confidentiality and integrity but does not affect availability.
Mitigation Recommendations
This vulnerability is fixed in avo versions 3.32.1 and 4.0.0.beta.51. Users should upgrade to at least version 3.32.1 to remediate this issue. No other mitigation or temporary workaround is indicated.
CVE-2026-55518: CWE-639: Authorization Bypass Through User-Controlled Key in avo-hq avo
Description
Avo is a framework to create admin panels for Ruby on Rails apps. Prior to 3.32.1 and 4.0.0.beta.51, Avo's association attach workflow checks attach_<association>? in the UI and GET /resources/:resource/:id/:related/new path, but the actual write endpoint, POST /resources/:resource/:id/:related, does not run the same authorization check before mutating the association through Avo::AssociationsController#create. An authenticated low-privileged Avo user can bypass hidden or disabled attach controls and directly attach related records to a parent record by sending a crafted POST request, which can lead to privilege escalation and cross-tenant data exposure where associations represent authorization-bearing relationships. This issue is fixed in versions 3.32.1 and 4.0.0.beta.51.
CVSS v3.1
Score 9.6critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-55518 is an authorization bypass vulnerability in the avo-hq Avo framework for Ruby on Rails admin panels. The flaw arises because the POST endpoint /resources/:resource/:id/:related used to attach associations does not enforce the same authorization checks as the UI and GET endpoints. This allows an authenticated user with low privileges to craft POST requests to attach related records directly, bypassing UI restrictions. Such unauthorized association mutations can lead to privilege escalation and cross-tenant data exposure when associations represent authorization boundaries. The vulnerability affects versions prior to 3.32.1 and 4.0.0.beta.51 and is fixed in those versions.
Potential Impact
An authenticated low-privileged user can bypass intended authorization controls to attach related records to parent records. This can result in privilege escalation and unauthorized cross-tenant data exposure where associations control access. The vulnerability has a high impact on confidentiality and integrity but does not affect availability.
Mitigation Recommendations
This vulnerability is fixed in avo versions 3.32.1 and 4.0.0.beta.51. Users should upgrade to at least version 3.32.1 to remediate this issue. No other mitigation or temporary workaround is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T22:44:22.284Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5ea72d1edb114c7fafa2
Added to database: 07/18/2026, 11:08:23 UTC
Last enriched: 07/25/2026, 22:49:11 UTC
Last updated: 08/31/2026, 22:52:12 UTC
Views: 98
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.