CVE-2026-56264
Analyzed Analyzed - Analysis Complete

JavaScript Execution in Crawl4AI Docker API

Vulnerability report for CVE-2026-56264, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-07-06

Assigner: VulnCheck

Description

Crawl4AI before 0.8.7 contains an arbitrary JavaScript execution vulnerability in the Docker API server's /execute_js endpoint, which accepts and executes arbitrary user-supplied JavaScript in the server's browser context with --disable-web-security enabled. An attacker can execute arbitrary JavaScript and, combined with the browser's relaxed security settings, perform server-side request forgery against internal services.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-07-06
Generated
2026-07-21
AI Q&A
2026-07-01
EPSS Evaluated
2026-07-19
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
kidocode crawl4ai to 0.8.7 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Crawl4AI before version 0.8.7 has a security flaw in its Docker API server's /execute_js endpoint. This endpoint allows execution of arbitrary JavaScript code supplied by a user within the server's browser context. Because the browser is run with the --disable-web-security flag enabled, it relaxes normal security restrictions, enabling an attacker to execute malicious JavaScript.

This vulnerability can be exploited to perform server-side request forgery (SSRF) attacks against internal services by leveraging the browser's relaxed security settings.

Detection Guidance

This vulnerability involves arbitrary JavaScript execution via the /execute_js endpoint in the Crawl4AI Docker API server. Detection can focus on monitoring network traffic or server logs for suspicious requests targeting this endpoint.

You can detect attempts to exploit this vulnerability by checking for HTTP requests to the /execute_js endpoint on the Crawl4AI Docker API server, especially those containing JavaScript payloads.

  • Use network monitoring tools (e.g., tcpdump, Wireshark) to filter HTTP requests to the /execute_js endpoint.
  • Example tcpdump command: tcpdump -i any -A -s 0 'tcp port 80 or tcp port 443' | grep '/execute_js'
  • Check server access logs for POST requests to /execute_js with suspicious payloads.
  • Use curl or similar tools to test if the endpoint is accessible and vulnerable by sending controlled JavaScript payloads.
Impact Analysis

An attacker exploiting this vulnerability can execute arbitrary JavaScript code on the server, potentially leading to unauthorized actions or data access.

Additionally, the attacker can perform server-side request forgery (SSRF) attacks, which may allow them to access internal services that are not normally exposed externally.

The CVSS scores indicate a high severity, with impacts on confidentiality, integrity, and availability, meaning the vulnerability can lead to significant compromise of the affected system.

Compliance Impact

The vulnerability allows arbitrary JavaScript execution and server-side request forgery, which can lead to unauthorized access to internal services and potentially sensitive data.

Such unauthorized access and potential data breaches could negatively impact compliance with data protection regulations like GDPR and HIPAA, which require strict controls over data confidentiality, integrity, and availability.

Exploitation of this vulnerability could result in exposure or manipulation of personal or protected health information, thereby violating these standards.

Mitigation Strategies

The primary mitigation is to upgrade Crawl4AI to version 0.8.7 or later, where this vulnerability has been fixed.

Additional immediate steps include disabling or restricting access to the /execute_js endpoint, enforcing authentication and authorization on the Docker API server, and avoiding running the server with --disable-web-security enabled.

Implement network-level controls to restrict access to the Crawl4AI Docker API server to trusted hosts only.

Review and apply security hardening measures such as input sanitization, path validation, and removing hardcoded secrets as recommended in the security advisory.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56264. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart