CVE-2026-55518

Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation

Published Jul 17, 2026 CVSS 3.1 · 9.6 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Avo is a framework for building admin panels in Ruby on Rails. Before version 3.32.1 and 4.0.0.beta.51, the framework’s association attach workflow performs a check for an attach_<association> parameter in the UI and the GET /resources/:resource/:id/:related/new endpoint. However, the actual write operation on POST /resources/:resource/:id/:related is handled by Avo::AssociationsController#create and lacks the same authorization verification. An authenticated user with lower privileges can therefore send a crafted POST request to attach any related record to a parent, bypassing hidden or disabled UI controls. This unauthorized manipulation can result in privilege escalation and cross‑tenant data exposure when the associations carry authorization‑bearing relationships.

Affected Systems

The affected product is Avo (avo-hq:avo). Versions prior to 3.32.1 and 4.0.0.beta.51 are vulnerable. All installations of these versions that expose the resource association endpoints are at risk.

Risk and Exploitability

The vulnerability carries a CVSS score of 9.6, indicating critical severity. EPSS is below 1 %, showing a low but non‑zero likelihood of exploitation. It is not listed in CISA’s KEV catalog. The likely attack vector is an authenticated user sending a crafted POST request to the /resources/:resource/:id/:related endpoint, inferred from the description. An attacker must first be authenticated within Avo; thereafter, by posting to /resources/:resource/:id/:related the attacker can manipulate associations and potentially gain higher privileges or access data outside their tenant. The flaw is exploitable without requiring additional privileges beyond the authenticated low‑privileged user, making it a significant risk for applications that rely on strict ownership checks for associations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Avo to version 3.32.1 or later, or 4.0.0.beta.51, which add the missing authorization check to the POST endpoint. This patch addresses weaknesses identified as CWE-639, CWE-862, and CWE-863.
  • Verify that all association attachment routes are protected by proper authorization logic and that any hidden or disabled UI controls do not accidentally expose the backend endpoints, ensuring compliance with CWE-862 and CWE-863 guidance.
  • Review and enforce that cross‑tenant data access is guarded by tenant isolation checks, ensuring that unauthorized users cannot attach records belonging to other tenants, thereby mitigating potential CWE-639 impacts.

Generated by OpenCVE AI on August 1, 2026 at 08:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8fq9-273g-6mrg Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Avo Hq
Avo Hq avo
Vendors & Products Avo Hq
Avo Hq avo
Type Values Removed Values Added
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.
Title Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation
Weaknesses CWE-639
CWE-862
CWE-863
References
Metrics cvssV3_1

{'score': 9.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 3:20 PM
Reserved
Jun 16, 2026, 10:44 PM
Status
Deferred
Published
Jul 17, 2026, 9:17 PM
Modified
Oct 24, 2026, 8:10 PM