CVE-2026-46552 is an authorization flaw in NocoDB affecting versions prior to 2026.04.1. Shared-base sessions were treated as if they had the same effective permissions as authenticated base viewers. In the affected implementation, requests authenticated only by a shared-base identifier were mapped to the viewer project role, and the access-control logic granted that role capabilities including listing base users and inviting new users. Because the authorization layer did not distinguish shared-link sessions from legitimate authenticated viewer sessions, an attacker possessing only a valid shared-base identifier could enumerate existing base members and send an invitation to an arbitrary email address. The invited recipient could then complete the standard signup and invitation redemption flow and become a real authenticated member of the base. This access could persist even after the owner revoked the original shared link.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.