High Info disclosure

CVE-2026-56259 — Crawl4AI - LLM Credential Exfiltration via base_url and Environment Variable Resolution

Crawl4AI before 0.8.8 contains credential exfiltration vulnerabilities in the Docker API server that allow attackers to redirect LLM API calls to attacker-controlled endpoints and read arbitrary environment variables. Attackers can exploit the unauthenticated /md, /llm, and /llm/job endpoints by supplying a malicious base_url parameter and setting api_token to env:VARIABLE_NAME to exfiltrate provider API keys and server secrets including JWT SECRET_KEY for authentication bypass.

Published Jul 12, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Crawl4AI

Crawl4AI and 1 more

CVSS base

8.2

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented mitigation — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Crawl4AI Crawl4AI, Kidocode Crawl4ai).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
Apply the documented mitigations until a definitive fix is available.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Crawl4AI	Crawl4AI	< 0.8.8	Vulnerable	CVE Program (cve.org) e CISA ADP
Kidocode	Crawl4ai	< 0.8.8	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.8	CVSS 4.0	High	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
8.8	CVSS 4.0	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
8.2	CVSS 3.1	High	3.9	4.2	disclosure@vulncheck.com via NIST National Vulnerability Database
8.2	CVSS 3.1	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for anomalous data read/export volumes and access to sensitive records.

web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · crawl4ai/crawl4ai
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
Fix documented
Oct 15, 2026 · NIST National Vulnerability Database
CVSS changed · 8.2
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Jul 12, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

github.com/unclecode/crawl4ai/security/advisories/GHSA-f989-c77f-r2cq
Vendor Advisory, Mitigation, vendor-advisory, NIST National Vulnerability Database
www.vulncheck.com/advisories/crawl4ai-llm-credential-exfiltration-via-base-url-and-envi
Third Party Advisory, third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Crawl4AI
every CVE for this vendor

Info disclosure
same class

CWE-200
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-56260 Crawl4AI - Arbitrary File Write via output_path Parameter Jul 12, 2026
High CVE-2026-56261 Crawl4AI - Server-Side Request Forgery via Webhook URLs Jul 10, 2026
Critical CVE-2026-57572 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args Jul 6, 2026
High CVE-2026-57573 Crawl4AI unauthenticated SSRF in Docker streaming crawl endpoint Jul 6, 2026
Critical CVE-2026-57571 Crawl4AI arbitrary file write via download filename path traversal Jul 6, 2026
Medium CVE-2026-56264 Crawl4AI - Arbitrary JavaScript Execution via /execute_js Endpoint Jun 30, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-56259 is "Crawl4AI - LLM Credential Exfiltration via base_url and Environment Variable Resolution", rated High. It affects Crawl4AI (Crawl4AI); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.