OCTOBER 9, 2026
Live Feed
Back to database
Case File

CVE-2026-100172

HIGH · CVSS 8.5 EPSS 0.27% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-25 · Last synced 2026-10-09

CyberRota Analysis

AI-Generated

The AIL Framework's Jinja2 templates are vulnerable to a stored cross-site scripting (XSS) attack due to improper handling of dynamic content in Bootstrap popover elements. This allows authenticated attackers to inject arbitrary HTML or JavaScript, which can execute in the context of a victim's session, potentially leading to data exfiltration or unauthorized actions. Organizations using the AIL Framework should prioritize patching this vulnerability to mitigate risks associated with user data and session integrity.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-100172
Severity
HIGH
CVSS
8.5
EPSS
0.27%
Java

Original NVD Description

The AIL Framework (ail-project/ail-framework) contains a stored cross-site scripting (XSS) vulnerability in two Jinja2 templates that render popovers for matched, tracked, or tagged content: var/www/templates/chats_explorer/block_message.html and var/www/templates/objects/item/show_item.html. In both templates, dynamic values associated with this content, including icon color, icon style, icon glyph, subtype, identifier, name, description, and matched value, are interpolated directly into the data-content HTML attribute of Bootstrap popover elements without appropriate output encoding. Because the popovers are configured with data-html="true", the content is interpreted as HTML in the victim's browser. An authenticated attacker who can influence matched, tracked, or tagged content may inject arbitrary HTML or JavaScript into these values. When a victim displays the affected popover, the injected markup may execute in the victim's session, potentially enabling data exfiltration or actions with the victim's privileges. The vulnerability is classified as stored XSS because the malicious payload can persist in the affected match, tracking, or tag-related data and be delivered to users who view the affected content.