CVE-2026-109238 unclecode CVE debrief

Who should care

Defenders responsible for Crawl4AI instances, especially those with link_preview_config enabled, should assess potential internal network impact and verify exposure. This includes operators managing Crawl4AI deployments, platform administrators, vulnerability management teams, and security teams responsible for monitoring and incident response.

Why it matters

Defenders should prioritize verifying exposure of Crawl4AI instances, especially those with link_preview_config enabled, and assess potential internal network impact due to the SSRF vulnerability.

• Potential internal network exposure through SSRF
• Possible access to private and cloud-metadata links
• Risk of unauthorized data access or leakage
• Need for verification of Crawl4AI instance exposure and vulnerability

Technical summary

The Crawl4AI library is vulnerable to server-side request forgery (SSRF) in versions 0.7.0 before 0.9.4. An attacker can exploit this vulnerability by enabling link_preview_config on /crawl requests and supplying a controlled page with include_external and include_patterns set. This allows the attacker to cause AsyncUrlSeeder to fetch internal, private, and cloud-metadata links and return their parsed head data.

Defensive priority

Defenders should prioritize verifying exposure of Crawl4AI instances, especially those with link_preview_config enabled, and assess potential internal network impact.

Recommended defensive actions

• Verify Crawl4AI instance exposure, especially with link_preview_config enabled
• Assess potential internal network impact
• Review and update Crawl4AI to version 0.9.4 or later
• Monitor for suspicious /crawl requests and AsyncUrlSeeder activity
• Perform vulnerability scanning for internal network exposure
• Implement compensating controls for exposed systems
• Track remediation progress and verify evidence of updates

Evidence notes

The CVE record and source item provide details on the SSRF vulnerability in Crawl4AI 0.7.0 before 0.9.4. Vendor advisories and third-party advisories offer additional context. Defenders should verify exposure of Crawl4AI instances, especially those with link_preview_config enabled, and assess potential internal network impact due to the SSRF vulnerability. Evidence is limited to public CVE details and may not reflect all affected systems or specific vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.