# CVE-2026-100172: Cross-site scripting in ail framework

> An authenticated attacker can inject malicious scripts into AIL Framework popovers, leading to code execution and data theft in victim sessions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-fg9r-9hmh-7x8c

## What is CVE-2026-100172?

CVE-2026-100172 is a high-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-100172?


## How do I fix CVE-2026-100172?

No fix has been published for CVE-2026-100172 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100172 being exploited?

There is no known exploitation of CVE-2026-100172 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100172 and fix it if it is affected.

What it is: CVE-2026-100172 is a high-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100172 in the wild and no public exploit code.

Affected product: ail framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100172/ (Markdown: https://insights.sbomify.com/CVE-2026-100172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100172
- OSV: https://osv.dev/vulnerability/CVE-2026-100172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100172/
Summaries are generated and may contain mistakes; the official description above is the record.
