CVE-2026-100176: ail framework · Cross-site Scripting
Affects ail frameworkSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ail projectail framework | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to the timeline feature to trusted users only and consider disabling or limiting the rendering of usernames from untrusted sources. Implement input sanitization or output encoding on usernames before rendering them in the DOM to prevent execution of malicious scripts.
Description
CVE-2026-100176 is a stored cross-site scripting (XSS) vulnerability in the AIL Framework's username timeline feature. Usernames imported from external sources are stored without sanitization and rendered unsafely in the analyst's browser using D3's html() method. An attacker can craft a malicious username containing HTML event handlers that execute arbitrary JavaScript when an authenticated analyst hovers over the timeline entry. Exploitation requires the victim to be authenticated and interact with the malicious entry. This can lead to session hijacking, data exfiltration, or unauthorized actions within the analyst's session.