CVE-2026-100174: ail framework · Cross-site Scripting
Affects ail frameworkSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 7.1 when convenient.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/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
Upgrade ail framework to 7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ail projectail framework | Affected
| Fixed in
|
GitHubail frameworkpkg:github/ail frameworkOther threats | 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
If you cannot patch yet, restrict permissions to create custom tags to trusted users only. Consider implementing input sanitization or escaping on tag names before inserting them into the DOM. Avoid using jQuery's html property with untrusted input; use text insertion methods instead.
Description
CVE-2026-100174 is a stored cross-site scripting (XSS) vulnerability in the AIL Framework's tag selector component. An authenticated user with permission to create custom tags can embed malicious JavaScript in a tag name. When another authenticated user views a page with the malicious tag, the script executes in their browser. This occurs because the tag name is inserted as raw HTML via jQuery's html property without proper sanitization. Exploitation can lead to arbitrary script execution within the application's origin, risking session hijacking and unauthorized data access.