Skip to content
Cloud

CVE-2026-56261

9.2
Critical
EPSS 0.51%Patch availableJul 11, 2026

SSRF in Crawl4AI allows internal and cloud metadata access via webhook URLs.

common questions

Is CVE-2026-56261 being exploited?

Not confirmed. CVE-2026-56261 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-56261?

CVE-2026-56261 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-56261?

Yes. A fix has been recorded for CVE-2026-56261. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-56261 affect?

CVE-2026-56261 affects Crawl4AI < 0.8.7, Self-hosted Crawl4AI Docker deployments, Endpoints: /crawl/job, /llm/job. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-56261?

Upgrade to Crawl4AI 0.8.7+, block outbound access to metadata/internal IPs, validate webhook URLs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Crawl4AI < 0.8.7Self-hosted Crawl4AI Docker deploymentsEndpoints: /crawl/job, /llm/job
impact

Attacker-controlled webhook URLs trigger server requests to internal IPs, Docker networks, and cloud metadata (169.254.169.254), risking credential/token exposure and internal service access.

action required

Immediate action required

affected versions
Crawl4AI Crawl4AI
  • affected< 0.8.7
vendor says fixed in0.8.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free