cve.bz

CVE-2026-55518 avo-hq avo: Missing Authorization

9.6 criticalEPSS 0.4%Fix available

Critical (9.6) in avo-hq avo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in avo 3.32.1, 4.0.0.beta.51.

On this page
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.

Severity

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-07-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-639 Authorization Bypass Through User-Controlled Key
CWE-862 Missing Authorization
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • avo (RubyGems): fixed in 3.32.1, 4.0.0.beta.51

Ask an AI about this CVE

Show the promptExplain CVE-2026-55518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55518?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55518?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55518 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
avo-hq avo>= 4.0.0.beta.1, < 4.0.0.beta.51
avo-hq avo< 3.32.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8fq9-273g-6mrgRubyGemsavo<3.32.13.32.1
GHSA-8fq9-273g-6mrgRubyGemsavo>=4.0.0.beta.1 <4.0.0.beta.514.0.0.beta.51

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON