{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100187 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100187 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-100187 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-100187 in the wild and no public exploit code.\n\nAffected product: ail framework. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100187/ (Markdown: https://insights.sbomify.com/CVE-2026-100187/index.md)","id":"CVE-2026-100187","markdown":"https://insights.sbomify.com/CVE-2026-100187/index.md","name":"CVE-2026-100187","record":{"aliases":["GHSA-8f5g-55q8-r2c9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"AIL Framework","requires_auth":"none","summary":"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.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AIL Framework Onion Module: Non-Onion URL Accepted as Crawler Task Due to Bypassed Domain Validation","id":"CVE-2026-100187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Stored Cross-Site Scripting (XSS) via Crawler Capture Import in AIL Framework showDomain Page","id":"CVE-2026-100190"},"packages":[],"prev":{"headline":"User Profile Builder \u003c= 4.0.3 - Unauthenticated Stored Cross-Site Scripting via First Name Field","id":"CVE-2026-100186"},"products":["ail framework"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["ail project"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-100187/"}