CVE-2026-115508 unclecode CVE debrief

Who should care

Defenders responsible for Crawl4AI deployments, particularly those using versions 0.7.0 before 0.9.5, should assess exposure and prioritize patching or mitigation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the vulnerability and implement necessary controls to prevent potential attacks.

Why it matters

Defenders should care about this vulnerability because it allows authenticated clients to submit malicious regular expressions that can freeze the entire server, potentially leading to denial of service attacks and impacting dependent services.

• Potential denial of service attacks against the API server
• Increased server load and resource utilization
• Possible impact on dependent services or applications

Technical summary

The Crawl4AI API server is vulnerable to a regular expression denial of service (ReDoS) attack in the /crawl endpoint. Authenticated clients can submit malicious regular expressions to cause catastrophic backtracking, freezing the server. This vulnerability is caused by inefficient regular expression complexity in the Docker API server. Defenders should prioritize patching or mitigating this vulnerability to prevent potential denial of service attacks. The vulnerability can be exploited by submitting malicious regular expressions via RegexExtractionStrategy.custom, RegexChunking.patterns or JsonCss, JsonXPath and JsonLxml schema regex fields.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability to prevent potential denial of service attacks.

Recommended defensive actions

• Patch Crawl4AI to version 0.9.5 or later
• Restrict access to the /crawl endpoint
• Monitor API server logs for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including affected versions and potential attack vectors. The vulnerability is confirmed in Crawl4AI versions 0.7.0 before 0.9.5. Defenders should verify the presence of affected versions in their environments and review official advisories for guidance. The ReDoS vulnerability can be exploited by submitting catastrophic-backtracking patterns via RegexExtractionStrategy.custom, RegexChunking.patterns or JsonCss, JsonXPath and JsonLxml schema regex fields against a C

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.