Loading vulnerability…
CVE-2026-55518 is an authorization bypass vulnerability in Avo, a framework for building admin panels for Ruby on Rails applications. In affected versions prior to 3.32.1 and prior to 4.0.0.beta.51 on the 4.0 beta branch, the association attach workflow enforced the attach_<association>? authorization check in the user interface and on the route used to render the attach form, but the corresponding mutating POST endpoint did not enforce the same check before updating the association in Avo::AssociationsController#create. As a result, an authenticated low-privileged user could bypass hidden or disabled attach controls by issuing a crafted POST request directly to the write endpoint and attach related records to a parent record without authorization. Where associations encode ownership, membership, assignment, or other authorization-bearing relationships, exploitation can result in privilege escalation and cross-tenant data exposure.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.