Loading vulnerability…
CVE-2026-45727 affects CloakBrowser versions prior to 0.3.28. The vulnerability is in the cloakserve CDP multiplexer, which uses the user-supplied fingerprint query parameter directly as a filesystem path component when creating Chrome profile directories. Because the input is not safely constrained to the configured data_dir, an unauthenticated attacker who can reach the cloakserve port can supply crafted path traversal sequences in fingerprint so that user_data_dir resolves outside the intended directory tree. When Chrome startup fails or when the process performs cleanup, cloakserve invokes shutil.rmtree() on the attacker-influenced path, which can delete directories outside the configured data directory. The issue is exacerbated by cloakserve binding to 0.0.0.0 by default, increasing the likelihood of remote 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.
2 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.