The Onion module in AIL Framework contained a performance shortcut in its URL extraction logic that accepted URLs as valid .onion targets based solely on a length check (exactly 69 characters) and a suffix check (ending in ".onion"), without performing proper hostname parsing or onion-domain validation. An unauthenticated attacker who could publish or control web content crawled by the framework could embed a crafted URL containing an IP address or non-onion hostname with a path ending in ".onion" that satisfied the length and suffix conditions. Such a URL would be extracted, its domain naively sliced from the string, and queued as a legitimate onion crawler task. This allowed unauthenticated content publishers to inject arbitrary non-onion targets into the crawler's task queue, influencing crawler behavior and potentially directing it toward unintended network resources. The vulnerability required no authentication, no user interaction, and only the ability to place crafted content in a location the framework would crawl. The security impact is a loss of integrity in the crawler's target selection: the framework processes and acts upon URLs that do not correspond to legitimate .onion services.
CVE-2026-100187
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 6.9
- EG Score
- 6.9MEDIUMmedium confidence
- EG Risk
- 46EG Risk 46/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 25, 2026
Last Modified
September 25, 2026
Advisory Details (1)
Auto-updated Sep 25, 2026commit 5c8a68b3d8c7 (ail-project/ail-framework)
Fix landed in ail-project/ail-framework commit 5c8a68b3d8c7 — awaiting tagged release
https://github.com/ail-project/ail-framework/commit/5c8a68b3d8c7d7b03e5febe4ac5b5aca91826adbVendor Advisories for CVE-2026-100187(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 19× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-10-04 00:47 UTCEG score recompute
- 2026-10-04 00:47 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 23:38 UTCEG score recompute
- 2026-10-02 23:38 UTCGHSA enrichment
- 2026-10-01 22:27 UTCEG score recompute
- 2026-10-01 22:27 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 21:17 UTCEG score recompute
- 2026-09-30 21:16 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 20:05 UTCEG score recompute
- 2026-09-29 20:05 UTCGHSA enrichment
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-28 18:56 UTCEG score recompute
- 2026-09-28 18:56 UTCGHSA enrichment
- 2026-09-28 13:50 UTCEPSS rescore
- 2026-09-27 17:47 UTCEG score recompute
- 2026-09-27 17:47 UTCGHSA enrichment
- 2026-09-26 16:38 UTCEG score recompute
- 2026-09-26 16:37 UTCGHSA enrichment
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-25 15:23 UTCEG score recompute
- 2026-09-25 14:54 UTCEG score recompute
- 2026-09-25 14:22 UTCEG score recompute
Show 2 moreShow fewer
- 2026-09-25 13:44 UTCEG score recompute
- 2026-09-25 13:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100187?
When was CVE-2026-100187 disclosed?
Is CVE-2026-100187 actively exploited?
What is the CVSS score of CVE-2026-100187?
How do I remediate CVE-2026-100187?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100187
Is Your Infrastructure Affected by CVE-2026-100187?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.