GHSA-j2qh-f73r-mg3q: Crawl4AI before 0.9.5 Improper Certificate Validation via Hard-coded Chromium Flags

Published Oct 29, 2026

Updated

Crawl4AI before 0.9.5 contains an improper certificate validation vulnerability that allows network attackers to intercept crawls because Chromium always launches with --ignore-certificate-errors. Man-in-the-middle or DNS-controlling attackers can serve forged content to the crawler and read cookies and headers sent, while hard-coded --no-sandbox also overrides CRAWL4AICHROMIUMSANDBOX.

Frequently Asked Questions

Which deployments are exposed?

Crawl4AI versions before 0.9.5 are affected when they crawl targets over networks where an attacker can perform a man-in-the-middle attack or control DNS resolution.

Is the default Chromium certificate-validation behavior affected?

Yes. Chromium is launched with the hard-coded --ignore-certificate-errors flag, so certificate errors are ignored during crawls.

Can CRAWL4AI_CHROMIUM_SANDBOX re-enable the Chromium sandbox?

No. The hard-coded --no-sandbox flag overrides CRAWL4AI_CHROMIUM_SANDBOX.

GHSA-j2qh-f73r-mg3q: Crawl4AI before 0.9.5 Improper Certificate Validation via Hard-coded Chromium Flags

Frequently Asked Questions

Which deployments are exposed?

Is the default Chromium certificate-validation behavior affected?

Can CRAWL4AI_CHROMIUM_SANDBOX re-enable the Chromium sandbox?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed?

Is the default Chromium certificate-validation behavior affected?

Can CRAWL4AI_CHROMIUM_SANDBOX re-enable the Chromium sandbox?