Crawl4AI
Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key
Crawl4AI before 0.8.7 contains an authentication bypass vulnerability due to a hardcoded default JWT signing key in the Docker API server. Attackers who know the default key can forge valid authentication tokens for any user, bypassing authentication and gaining full access to protected functionality.
First public PoC
43 daysafter publication · 3 Aug 2026 · nuclei template
Public PoCs10 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS9.8critical · scored by CNA · CWE-798
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Crawl4AI Crawl4AI
- < 0.8.7
Fixed in 0.8.7
Mitigation
Upgrade Crawl4AI to 0.8.7 or later.
References
- Vendor advisory github.com/unclecode/crawl4ai/security/advisor…
Timeline
Days relative to CVE publicationFirst public PoC 43 days after publication; not in CISA KEV. First PoC: nuclei template: Crawl4AI < 0.8.7 - Hardcoded JWT Signing Key Authentication Bypass (nuclei template, 3 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Crawl4AI < 0.8.7 - Hardcoded JWT Signing Key Authentication Bypass | 3 Aug 2026 | 14 Nov 2026 |