CVE-2026-56265PYSEC-2026-798GHSA-365W-HQF6-VXFGGHSA-53RG-46CM-4G2VGHSA-8QRG-7J2F-RF2HGHSA-F23G-2F38-GG94GHSA-G2PV-76HM-J4X9GHSA-R9HW-78Q5-478GGHSA-XRFJ-6M49-WFMMPYSEC-2026-229PYSEC-2026-230PYSEC-2026-239PYSEC-2026-3443PYSEC-2026-3449PYSEC-2026-596
Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.8.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 Nuclei template
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Crawl4AI Crawl4AI
fixed in 0.8.7
- crawl4aiPyPI
fixed in 0.8.7