Skip to main content
Vulnerability Database/CVE-2026-100172

CVE-2026-100172: AIL Framework Stored XSS Vulnerability

CVE-2026-100172 is a stored XSS flaw in AIL Framework that allows attackers to inject malicious scripts through Jinja2 templates. This post explains its impact, affected components, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100172 Overview

CVE-2026-100172 is a stored cross-site scripting (XSS) vulnerability in the AIL Framework (ail-project/ail-framework), an open-source analysis platform for information leaks. The flaw resides in two Jinja2 templates, var/www/templates/chats_explorer/block_message.html and var/www/templates/objects/item/show_item.html, which render Bootstrap popovers for matched, tracked, or tagged content. Dynamic values are interpolated directly into the data-content attribute of popover elements configured with data-html="true", causing injected markup to execute as HTML in the victim's browser. The weakness is classified under [CWE-79].

Critical Impact

An authenticated attacker who can influence matched, tracked, or tagged content can store HTML or JavaScript payloads that execute in the sessions of users viewing the affected popovers.

Affected Products

  • AIL Framework (ail-project/ail-framework) prior to commit ee63a0a96646790255e038f5ca5dd0ab5fe98db2
  • var/www/templates/chats_explorer/block_message.html template
  • var/www/templates/objects/item/show_item.html template

Discovery Timeline

  • 2026-09-25 - CVE-2026-100172 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-100172

Vulnerability Analysis

The AIL Framework displays extracted matches, trackers, and tags using Bootstrap popovers that render dynamic metadata on hover. Both affected templates build the popover data-content attribute by concatenating raw values from the extracted_matches structure, including icon.color, icon.style, icon.icon, subtype, id, name, description, and the matched value r[1]. Because data-html="true" instructs Bootstrap to parse the attribute as HTML, any markup inside those values is injected into the DOM when a victim triggers the popover. The payload persists in the underlying match, tracker, or tag data, qualifying this as stored XSS rather than reflected injection.

Root Cause

The root cause is missing output encoding in Jinja2 templates. While Jinja2 autoescaping handles the initial HTML context, the values are placed inside an HTML attribute that is later re-parsed as HTML by Bootstrap. A single layer of escaping is insufficient. The fix applies |forceescape|forceescape to the affected fields so that angle brackets and quotes are encoded twice, surviving both the attribute context and the subsequent HTML parse performed by the popover widget.

Attack Vector

An authenticated attacker who can push content into AIL's processing pipeline, or register a tracker, tag, or match with attacker-controlled fields, can embed HTML or JavaScript into any of the vulnerable attributes. When another authenticated analyst views the item or chat message and hovers over the affected span, the browser renders the injected markup in the victim's session. This can enable session theft, pivoting to additional AIL actions with the victim's privileges, or exfiltration of analyst-visible intelligence data.

text
// Patch excerpt - var/www/templates/chats_explorer/block_message.html
- fill="{{ message['extracted_matches'][r[0]]['icon']['color'] }}"
+ fill="{{ message['extracted_matches'][r[0]]['icon']['color']|forceescape|forceescape }}"
- class="{{ message['extracted_matches'][r[0]]['icon']['style'] }}"
+ class="{{ message['extracted_matches'][r[0]]['icon']['style']|forceescape|forceescape }}"
- >{{ message['extracted_matches'][r[0]]['icon']['icon'] }}<
+ >{{ message['extracted_matches'][r[0]]['icon']['icon']|forceescape|forceescape }}<
- </div>{{ message['extracted_matches'][r[0]]['subtype'] }}</div>
+ </div>{{ message['extracted_matches'][r[0]]['subtype']|forceescape|forceescape }}</div>
- {{ message['extracted_matches'][r[0]]['id'] }}
+ {{ message['extracted_matches'][r[0]]['id']|forceescape|forceescape }}
- <b>{{ r[1] }}</b>
+ <b>{{ r[1]|forceescape|forceescape }}</b>

Source: AIL Framework commit ee63a0a9

Detection Methods for CVE-2026-100172

Indicators of Compromise

  • Match, tracker, tag, or extracted content records containing HTML tags such as <script, <img, <svg, or event handler attributes like onerror=, onload=, or onmouseover=.
  • Unexpected outbound HTTP requests from analyst browsers to attacker-controlled hosts shortly after viewing an item or chat message in AIL.
  • Jinja2 template output in rendered pages where data-content attributes contain unescaped < or > characters.

Detection Strategies

  • Grep the AIL datastore and tracker configuration for HTML or JavaScript syntax in name, description, subtype, id, icon.color, icon.style, and icon.icon fields.
  • Review web server access logs for AIL endpoints serving show_item and chats_explorer/block_message views, correlating with sessions that trigger unusual outbound DOM-initiated requests.
  • Deploy a Content Security Policy (CSP) in report-only mode on the AIL web UI to surface inline script execution attempts.

Monitoring Recommendations

  • Monitor browser telemetry on analyst endpoints for script execution originating from AIL hostnames.
  • Alert on new tracker, tag, or match submissions whose field values fail HTML-sanitization validation.
  • Track AIL application version and template file hashes to confirm patched builds are deployed.

How to Mitigate CVE-2026-100172

Immediate Actions Required

  • Upgrade AIL Framework to a build that includes commit ee63a0a96646790255e038f5ca5dd0ab5fe98db2 or later.
  • Audit existing extracted_matches, trackers, and tags for stored HTML payloads and purge or sanitize any found.
  • Restrict AIL web UI access to trusted analysts over authenticated, network-segmented channels.

Patch Information

The maintainers fixed the issue by applying |forceescape|forceescape to every dynamic value interpolated into the popover data-content attribute in both var/www/templates/chats_explorer/block_message.html and var/www/templates/objects/item/show_item.html. Full patch details are available in the AIL Framework commit ee63a0a9.

Workarounds

  • Temporarily patch the two Jinja2 templates in place by adding |forceescape|forceescape filters to the affected expressions, mirroring the upstream commit.
  • Disable or hide the extracted-matches popovers in the UI until the patched version is deployed.
  • Enforce a strict Content Security Policy that forbids inline scripts and restricts script sources on the AIL web interface.
bash
# Pull the patched AIL Framework and redeploy
git fetch origin
git checkout ee63a0a96646790255e038f5ca5dd0ab5fe98db2
# Verify the fix is present in the templates
grep -n 'forceescape|forceescape' \
  var/www/templates/chats_explorer/block_message.html \
  var/www/templates/objects/item/show_item.html
# Restart the AIL web service
sudo systemctl restart ail-framework

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.