CVE-2026-53753
Sandbox escape in Crawl4AI enables unauthenticated RCE via crafted schema (pre-0.8.7).
Is CVE-2026-53753 being exploited?
Not confirmed. CVE-2026-53753 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.9% probability of exploitation in the next 30 days.
How severe is CVE-2026-53753?
CVE-2026-53753 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53753?
Yes. A fix has been recorded for CVE-2026-53753. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53753 affect?
CVE-2026-53753 affects Crawl4AI (prior to 0.8.7). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53753?
Upgrade to 0.8.7+; verify deployments.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated RCE on host via POST /crawl with crafted extraction schema; sandbox bypass via AST validator.
Patch when possible
- affected< 0.8.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.