Crawl4AI 0.7.0 before 0.9.5 contains an inefficient regular expression complexity vulnerability in the Docker API server that allows authenticated API clients to supply unbounded regular expressions in /crawl request bodies. Attackers can submit catastrophic-backtracking patterns via RegexExtractionStrategy.custom, RegexChunking.patterns or JsonCss, JsonXPath and JsonLxml schema regex fields against a crafted page to freeze the entire server, including /health.
CVE-2026-115508
MEDIUMPre-NVD 6.56.5Trending — 3 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-22. A secondary CVSS source baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-108340 (ENISA EUVD) · GHSA-q4c3-mqc5-j3m8 (GitHub Security Advisories)Source: ENISA EUVD
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 45EG Risk 45/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity65% × 45%Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.5%
- EPSS %ILE
- 39th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 22, 2026
Last Modified
October 29, 2026
Advisory Details (5)
Auto-updated Oct 22, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
Web page
Crawl4AI 0.7.0 before 0.9.5 ReDoS via /crawl Regex Fields | Advisories | VulnCheck
https://www.vulncheck.com/advisories/crawl4ai-0.7.0-before-0.9.5-redos-via-crawl-regex-fieldsWeb page
GitHub - unclecode/crawl4ai: Open-source web crawler and scraper for LLMs and AI agents: any website into clean, LLM-ready Markdown. Run it yourself, or use Crawl4AI Cloud with one key. Join our Discord https://discord.gg/VuxzM8mtf · GitHub
https://github.com/unclecode/crawl4aiGitHub release Patch Available
Release v0.9.5
Patch available: unclecode/crawl4ai v0.9.5
https://github.com/unclecode/crawl4ai/releases/tag/v0.9.5GitHub commit Patch Available
commit 8aea2006e2cd (unclecode/crawl4ai)
Patch available: unclecode/crawl4ai v0.9.5 (contains commit 8aea2006e2cd)
https://github.com/unclecode/crawl4ai/commit/8aea2006e2cdb96a185e50b20633fc323dff6429GitHub advisoryMentions a patch (unverified)🟡 PoC Available
ReDoS via untrusted regex patterns freezes the Docker server · Advisory · unclecode/crawl4ai · GitHub
Affected: 0.9.5.
https://github.com/unclecode/crawl4ai/security/advisories/GHSA-j843-8p47-rhxpVendor Advisories for CVE-2026-115508(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 23× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-29 04:29 UTCEG score recompute
- 2026-10-29 04:29 UTCGHSA enrichmentGHSA-q4c3-mqc5-j3m8 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-29 03:25 UTCEG score recompute
- 2026-10-29 03:25 UTCGHSA enrichmentGHSA-q4c3-mqc5-j3m8 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-29 02:44 UTCEG score recompute
- 2026-10-29 02:44 UTCGHSA enrichmentGHSA-q4c3-mqc5-j3m8 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-25 14:50 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-23 13:28 UTCEG score recompute
- 2026-10-23 13:28 UTCGHSA enrichmentGHSA-q4c3-mqc5-j3m8 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-22 20:47 UTCEG score recompute
- 2026-10-22 19:26 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
- 2026-10-22 19:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-115508?
CVE-2026-115508 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. Crawl4AI 0.7.0 before 0.9.5 contains an inefficient regular expression complexity vulnerability in the Docker API server that allows authenticated API clients to supply unbounded regular expressions in /crawl request bodies. Attackers can submit catastrophic-backtracking patterns via…
When was CVE-2026-115508 made public?
CVE-2026-115508 was made public on October 2, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-115508 actively exploited?
CVE-2026-115508 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115508?
CVE-2026-115508 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-115508?
A fix for CVE-2026-115508 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115508 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-115508
Is Your Infrastructure Affected by CVE-2026-115508?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.