Loading vulnerability…
CVE-2026-56258 affects Crawl4AI versions before 0.8.8. The vulnerability is an arbitrary file write flaw in the screenshot and PDF endpoints involving the output_path parameter. Due to insufficient path validation, symlink following, and a time-of-check-time-of-use (TOCTOU) race condition, an unauthenticated remote attacker can cause the application to write files outside the intended directory. The issue arises when attacker-controlled output_path handling does not safely constrain filesystem targets and can be raced or redirected via symlinks, enabling writes to unintended locations on the host.
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.
3 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.