# CVE-2026-100187: AIL Framework Onion Module: Non-Onion URL Accepted as Crawler Task Due to Bypassed Domain Validation

> Unauthenticated attackers can inject non-onion URLs into the AIL Framework crawler queue by bypassing domain validation, potentially directing the crawler to unintended network resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-8f5g-55q8-r2c9

## What is CVE-2026-100187?

CVE-2026-100187 is a medium-severity server-side request forgery vulnerability in ail framework, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-100187?


## How do I fix CVE-2026-100187?

No fix has been published for CVE-2026-100187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100187 being exploited?

There is no known exploitation of CVE-2026-100187 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100187 and fix it if it is affected.

What it is: CVE-2026-100187 is a medium-severity server-side request forgery vulnerability in ail framework, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100187 in the wild and no public exploit code.

Affected product: ail framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100187/ (Markdown: https://insights.sbomify.com/CVE-2026-100187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100187
- OSV: https://osv.dev/vulnerability/CVE-2026-100187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100187/
Summaries are generated and may contain mistakes; the official description above is the record.
