CVE-2026-53753 json
Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API
published 4mo ago modified 17d ago also EUVD-2026-38569 , GHSA-qxjp-w3pj-48m7 , PYSEC-2026-319
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.7, the _safe_eval_expression() function in the computed fields feature uses an AST validator that only blocks attributes starting with underscore. Python generator and frame object attributes (gi_frame, f_back, f_builtins) do NOT start with underscore, enabling a complete sandbox escape to achieve arbitrary code execution. The attack requires no authentication (JWT disabled by default) and is triggered via POST /crawl with a crafted extraction schema. This vulnerability is fixed in 0.8.7.
Patch / fix
- pypi crawl4ai 0.8.7
- kidocode crawl4ai 0.8.7
- github.com/unclecode/crawl4ai#1855 pull request
- github.com/unclecode/crawl4ai#1886 pull request
Is CVE-2026-53753 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
2.90% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/unclecode/crawl4ai/security/advisories/GHSA-qxjp-w3pj-48m7 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | crawl4ai | <0.8.7 |
0.8.7 |
Affected products
- unclecode crawl4ai
Classification
References
-
github.com
/unclecode/crawl4ai/pull/1855
web
-
github.com
/unclecode/crawl4ai/pull/1886
web
-
github.com
/unclecode/crawl4ai/security/advisories/GHSA-qxjp-w3pj-48m7
exploit, web, third-party-advisory, mitigation
-
nvd.nist.gov
/vuln/detail/CVE-2026-53753
advisory
-
github.com
/advisories/GHSA-qxjp-w3pj-48m7
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/crawl4ai/PYSEC-2026-319.yaml
web
-
github.com
/unclecode/crawl4ai
package
-
pypi.org
/project/crawl4ai
web, package
Sources
- CVE List CVE-2026-53753
- GitHub Advisory GHSA-qxjp-w3pj-48m7
- NVD CVE-2026-53753
- OSV PYSEC-2026-319
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.