# Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args

Advisory record · `GHSA-r253-r9jw-qg44`

- **Identifiers:** `GHSA-r253-r9jw-qg44` · `CVE-2026-57572` · `PYSEC-2026-2139`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-88](https://cwe.mitre.org/data/definitions/88.html) · [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md) · [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 18 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Jun 2026, 17:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `crawl4ai` (PyPI): affected `<0.9.0`; fixed in `0.9.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Crawl4AI versions before 0.9.0 accept a request-supplied browser_config.extra_args in the Docker API, which passes values into Chromium launch arguments. An unauthenticated attacker who can reach the API can inject Chromium switches that make Chromium run an attacker-chosen command as the container's runtime user. Upgrade crawl4ai to 0.9.0, which rejects requests that set extra_args; enabling the CRAWL4AI_API_TOKEN authentication and restricting network access to the API also help.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0094, the 61st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r253-r9jw-qg44)

## Sources

- [GitHub Advisory Database: GHSA-r253-r9jw-qg44](https://github.com/advisories/GHSA-r253-r9jw-qg44)
- [OSV: GHSA-r253-r9jw-qg44](https://osv.dev/vulnerability/GHSA-r253-r9jw-qg44)
- <https://github.com/unclecode/crawl4ai/security/advisories/GHSA-r253-r9jw-qg44>
- <https://github.com/unclecode/crawl4ai>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r253-r9jw-qg44>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r253-r9jw-qg44/>. Everything for agents: <https://agentprime.io/llms.txt>.