CVE-2026-109239

5.3Medium

Published 12 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

5.3Medium

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: Limited impact
Weakness: CWE-918

Impact

Unauthenticated remote attackers can bypass Docker egress controls to scan internal services, loopback interfaces, or cloud metadata endpoints. They only need network access to trigger requests with robots.txt checking enabled.

Root cause

The RobotsParser.can_fetch function fails to block redirects or DNS rebinding to internal and sensitive IP ranges when retrieving robots.txt.

Affected systems

Crawl4AI before version 0.9.4

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Fix & remediation

Upgrade Crawl4AI to version 0.9.4 or later. If you cannot patch immediately, disable the check_robots_txt option in your crawling configuration.

shell

$ pip install --upgrade 'crawl4ai>=0.9.4'

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

Crawl4AI before 0.9.4 contains a blind server-side request forgery vulnerability in RobotsParser.can_fetch that lets unauthenticated attackers bypass Docker server egress controls. Attackers can enable check_robots_txt and use redirects or DNS rebinding to reach internal, loopback, or cloud-metadata addresses for service discovery.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-109239