CVE-2026-57572CVSS 10.0 Critical2026-07-07
Crawl4AI Docker API Argument Injection Leading to Arbitrary Command Execution
In Crawl4AI prior to version 0.9.0, the Docker API server contains an argument injection (CWE-88) security flaw. The API has no authentication enabled by default and accepts the browser_config.extra_args parameter supplied in requests, which is passed directly into Chromium's launch arguments. An attacker can inject Chromium launch switches and, combined with the --no-zygote parameter to replace the subprocess launch command, cause Chromium to fork or exec attacker-controlled commands as the container runtime user. Because no authentication is required, a single request can lead to arbitrary command execution. The vulnerability affects all Crawl4AI users who have not updated to 0.9.0, particularly deployments exposing the Docker API service. An attacker needs no user interaction and can execute arbitrary code remotely with a crafted request, gaining full control of the container environment.
Component
Crawl4AI is an open-source web crawler and scraping tool for large language models (LLMs), designed to provide LLM-friendly data collection services.
Risks
- Complete system control: An attacker can execute arbitrary code inside the container, and depending on container runtime user privileges, install programs, view/modify/delete data or create new accounts with full privileges
- Unauthenticated remote attack: Because the Docker API has no authentication enabled by default, an attacker can launch the attack without any credentials
- Container escape risk: With improper container configuration, an attacker may use this vulnerability to escape to the host and threaten the entire infrastructure
Source
Remediation- Immediately upgrade Crawl4AI to version 0.9.0 or later
- Enable authentication for the Docker API and restrict access permissions
- Apply strict allowlist validation or filtering to the incoming browser_config.extra_args parameter
CVE-2026-42341CVSS 9.8 Critical2026-07-07
FOSSBilling Unauthenticated Payment Bypass Leading to Account Credit Tampering
In FOSSBilling versions 0.6.0 through 0.7.2, the IPN callback endpoint lacks authentication for a critical function (CWE-306), resulting in an unauthenticated payment bypass. When the Custom payment adapter is enabled, an attacker can send a single carefully crafted HTTP request to mark any unpaid invoice as paid and credit the associated customer account, without making an actual payment. The vulnerability affects all FOSSBilling users who have not updated to 0.8.0. An attacker can trigger it remotely without authentication, directly bypassing business logic and undermining the integrity of financial data.
Component
FOSSBilling is a free open-source billing and client management system widely used to manage invoices, payments and customer accounts.
Risks
- Financial loss and fraud: An attacker can mark unpaid invoices as paid, causing revenue loss for the service provider
- Account credit tampering: An attacker can arbitrarily increase customer account credit, undermining the fairness and accuracy of the billing system
- Unauthenticated remote attack: An attacker needs no credentials and can exploit the vulnerability simply by crafting a specific HTTP request, with no user interaction
Source
Remediation- Immediately upgrade FOSSBilling to version 0.8.0 or later to fix the vulnerability
- If an immediate upgrade is not possible, disable the Custom payment gateway (if not actively used)
- Restrict access to /ipn.php at the web server level (for example through an IP allowlist), noting that this may interfere with legitimate payment callback handling