AIL Framework CVE-2026-100172

Requires an authenticated attacker (PR:L) who can influence content that AIL matches, tracks, or tags - specifically the fields interpolated into Bootstrap popovers rendered by var/www/templates/chats_explorer/block_message.html and var/www/templates/objects/item/show_item.html (icon color/style/glyph, subtype, identifier, name, description, and matched value). Exploitation is enabled by the popover configuration data-html="true", which causes the data-content attribute to be parsed as HTML. It also requires victim interaction (UI:P): a victim analyst must open the affected chat message or item view so the popover renders (typically on hover). It does NOT require a special non-default configuration - the vulnerable popovers are standard rendering paths - but it is limited to versions before the fix commit ee63a0a and to sessions of users who view attacker-influenced matched/tracked/tagged content.

This is a moderate-risk stored XSS in a niche threat-intelligence tool, not an emergency. The vendor-supplied CVSS 4.0 vector (8.5, AV:N/AC:L/PR:L/UI:P/VC:H/VI:H) rates it High, but that VC:H/VI:H rating is aggressive for browser-context XSS whose real impact is script execution in another authenticated analyst's session rather than full compromise of the vulnerable system's data. There is no EPSS score, no CISA KEV listing, and no public exploit code identified at time of analysis, so no evidence of active or automatable exploitation exists. Two mitigating signals bound real-world risk: exploitation is authenticated (PR:L - the attacker must be able to influence matched/tracked/tagged content inside AIL) and requires victim interaction (UI:P - a victim analyst must display/hover the affected popover). The patch is confirmed available (vendor commit ee63a0a). Net: a real, verifiable bug worth patching on a normal cadence, but not a widespread-exploitation priority given the small deployment footprint and the authenticated + interaction preconditions.

An authenticated user (or an actor who can seed content that AIL's trackers/taggers will match) plants a payload such as an icon color, subtype, tracker name/description, or matched value containing HTML like <img src=x onerror=...>. Because the popover uses data-html="true" and the values are interpolated into the data-content attribute without output encoding, the markup persists in the match/tracking data. When an analyst later views the chat message or item and the popover renders, the injected JavaScript executes in that analyst's authenticated session. No public POC is currently identified, but the patch diff clearly shows the unescaped sinks.