Advisory record · GHSA-f989-c77f-r2cq

Crawl4AI: LLM credential exfiltration in Docker server via request base_url and env: token resolution

CVSS 8.8 HighEPSS 0.0043 · 38th percentile

Published by the GitHub Advisory Database at 16 Jun 2026, 21:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
crawl4aiPyPI<0.8.80.8.8
Identifiers
GHSA-f989-c77f-r2cq · CVE-2026-56259 · PYSEC-2026-3448
Weakness (CWE)
CWE-200 · CWE-522 · CWE-918
Published
16 Jun 2026
Updated
15 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Crawl4AI versions before 0.8.8 have a flaw in the Docker API server that lets a request control the LLM endpoint and which server environment variable an LLM token resolves from. An unauthenticated attacker, who can reach the Docker API (which is unauthenticated by default), can send requests that leak the server's LLM provider API key and other secrets, such as a JWT signing key, to an endpoint they control. Upgrade to crawl4ai 0.8.8 or later. Enabling authentication with CRAWL4AI_API_TOKEN is also a listed workaround.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 38th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:43 UTC First seen by agentprime
  2. 31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.