cve.bz

CVE-2026-56261 kidocode crawl4ai: SSRF

9.2 criticalEPSS 0.5%Fix available

Critical (9.2) in kidocode crawl4ai. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in crawl4ai 0.8.7.

On this page
Crawl4AI before 0.8.7 contains a server-side request forgery (SSRF) vulnerability in the Docker API server's /crawl/job and /llm/job endpoints, which accept webhook URLs without destination validation. An attacker can supply webhook URLs pointing to private or internal IP ranges, Docker networks, or cloud metadata endpoints (e.g. 169.254.169.254), causing the server to make requests to internal services and potentially expose cloud metadata.

Severity

CVSS 4.0

9.2 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-56261 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56261?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56261?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56261 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Crawl4AIbefore 0.8.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-365w-hqf6-vxfgPyPIcrawl4ai<0.8.70.8.7
GHSA-8qrg-7j2f-rf2hPyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-229PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-230PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-239PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-3443PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-3449PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-596PyPIcrawl4ai<0.8.70.8.7
PYSEC-2026-798PyPIcrawl4ai<0.8.70.8.7

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON