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 describes an authorization bypass in avo-hq's avo framework prior to versions 3.32.1 and 4.0.0.beta.51. The attach workflow verifies authorization on UI and GET requests but fails to do so on the POST endpoint that modifies associations. Consequently, a low-privileged authenticated user can craft POST requests to attach related records directly, bypassing UI restrictions. This flaw can result in privilege escalation and unauthorized cross-tenant data exposure when associations control access rights. The issue is resolved by adding proper authorization checks on the POST /resources/:resource/:id/:related endpoint in the fixed versions.
Potential Impact
An attacker with low privileges who is authenticated in avo can bypass intended UI restrictions to attach related records to parent records without proper authorization. This can lead to privilege escalation within the application and exposure of data across tenants if associations govern access control. The confidentiality and integrity of data are severely impacted, but availability is not affected.
Mitigation Recommendations
This vulnerability is fixed in avo versions 3.32.1 and 4.0.0.beta.51. Users should upgrade to at least these versions to remediate the issue. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated in the vendor advisory, but the fixed versions are clearly identified.
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
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-55518 describes an authorization bypass in avo-hq's avo framework prior to versions 3.32.1 and 4.0.0.beta.51. The attach workflow verifies authorization on UI and GET requests but fails to do so on the POST endpoint that modifies associations. Consequently, a low-privileged authenticated user can craft POST requests to attach related records directly, bypassing UI restrictions. This flaw can result in privilege escalation and unauthorized cross-tenant data exposure when associations control access rights. The issue is resolved by adding proper authorization checks on the POST /resources/:resource/:id/:related endpoint in the fixed versions.
Potential Impact
An attacker with low privileges who is authenticated in avo can bypass intended UI restrictions to attach related records to parent records without proper authorization. This can lead to privilege escalation within the application and exposure of data across tenants if associations govern access control. The confidentiality and integrity of data are severely impacted, but availability is not affected.
Mitigation Recommendations
This vulnerability is fixed in avo versions 3.32.1 and 4.0.0.beta.51. Users should upgrade to at least these versions to remediate the issue. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated in the vendor advisory, but the fixed versions are clearly identified.
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/18/2026, 11:49:35 UTC
Last updated: 07/18/2026, 13:34:58 UTC
Views: 4
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.