CVE-2026-18972 is an authenticated identity-spoofing vulnerability in Velociraptor affecting versions prior to 0.77.2. The flaw allows a logged-in attacker to impersonate another GUI user by supplying the custom request header "Grpc-Metadata-USER". Because the application trusts this header for user identity, an attacker with low privileges can cause requests to be processed as though they originated from a different user, including a more privileged account. This can result in full account takeover of administrative GUI sessions or identities.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authenticated identity-spoofing vulnerability affecting Velociraptor versions prior to 0.77.2.
An authenticated identity-spoofing vulnerability identified as CVE-2026-18972 affecting Velociraptor.
An authentication/identity spoofing vulnerability in Velociraptor that allows a low-privileged authenticated user to impersonate another GUI user via the Grpc-Metadata-USER header, potentially leading to administrator account takeover.
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.