CVE Intelligence
Analysis AI-assisted

CVE-2026-56265: Crawl4AI Docker API Authentication Bypass via Hardcoded JWT Signing Key

Crawl4AI versions before 0.8.7 ship a hardcoded default JWT signing key in their Docker API server. Anyone who knows that key can forge tokens for any user and bypass authentication. The record rates it critical (CVSS 3.1 score 9.8), and no confirmed exploitation appears in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-56265 affects the Crawl4AI project, specifically its Docker API server. According to the record, versions before 0.8.7 use a hardcoded default JWT signing key, so anyone who knows that key can produce authentication tokens that the server accepts.

Impact

  • Attackers who know the default key can forge valid tokens for any user.
  • A forged token bypasses authentication and gives access to protected functionality.
  • The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes network reachability, low complexity, no privileges required and no user interaction, with high impact on confidentiality, integrity and availability.

Affected products and versions

  • Product: Crawl4ai, listed in the record under the vendor name Kidocode, with versions less than 0.8.7.
  • Upstream project: unclecode/crawl4ai.

Exploitation status

  • The CISA KEV catalog does not list this CVE according to the record.
  • No confirmed exploitation in the wild appears in the sources consulted.

Remediation and mitigation

  • Upgrade to Crawl4AI 0.8.7 or later. The affected range implies that 0.8.7 is the first unaffected release; confirm this against the vendor advisory GHSA-365w-hqf6-vxfg.
  • Make sure no deployment still runs with the default signing key. Configure a unique, high-entropy secret for each environment.
  • Treat tokens issued while a default key was in use as potentially untrustworthy, and rotate the signing secret after upgrading.
  • Limit network exposure of the Docker API server to trusted networks until the upgrade is complete.

Detection guidance

  • Review API server logs for authenticated sessions from unexpected sources or for user identities that do not match known accounts.
  • Audit container configuration and environment variables to confirm whether the JWT secret was left at a default or shared value.

Limitations of the available information

  • The record contains no EPSS score and no SSVC data, so exploitation likelihood is unknown.
  • The record does not state the exact default key value, token claim structure, or a fixed-version number beyond the 'before 0.8.7' range.
  • Whether the fix is delivered exactly in 0.8.7 is an inference from the affected range and should be confirmed in the vendor advisory.

Frequently asked questions

What is the root cause of CVE-2026-56265?

According to the record, the Crawl4AI Docker API server uses a hardcoded default JWT signing key, which is classified as CWE-798 (Use of Hard-coded Credentials).

Which versions are affected?

The record lists Crawl4ai versions less than 0.8.7 as affected.

Is this vulnerability being actively exploited?

The record shows it is not listed in CISA KEV, and no confirmed exploitation appears in the sources consulted.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.