{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100176 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100176 is a high-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-100176 and fix it if it is affected.\n\nWhat it is: CVE-2026-100176 is a high-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-100176 in the wild and no public exploit code.\n\nAffected product: ail framework. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100176/ (Markdown: https://insights.sbomify.com/CVE-2026-100176/index.md)","id":"CVE-2026-100176","markdown":"https://insights.sbomify.com/CVE-2026-100176/index.md","name":"CVE-2026-100176","record":{"aliases":["GHSA-gr26-vj67-v262"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AIL Framework","requires_auth":"none","summary":"Stored XSS in AIL Framework allows attackers to execute arbitrary JavaScript in an analyst's browser via crafted usernames, leading to session hijacking or data exfiltration.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The AIL Framework's username timeline feature is vulnerable to stored cross-site scripting (XSS). Usernames imported from chats and crawled forums are stored without character restrictions. When an authenticated analyst views the username timeline, the application renders these stored usernames into the DOM using D3's html() method in the tooltip. Because the username value (d.obj) is interpolated directly into an HTML string without sanitization, a crafted username containing HTML event handlers (e.g., \u003cimg src=x onerror=alert(1)\u003e) will execute arbitrary JavaScript in the analyst's browser when the analyst hovers over the corresponding timeline entry. The attack requires the victim to be an authenticated analyst with access to the timeline view and to interact with the malicious timeline entry (hover). Successful exploitation can lead to session hijacking, data exfiltration, or unauthorized actions performed within the analyst's authenticated session. The vulnerability resides in the client-side JavaScript file var/www/static/js/d3/timeline_basic.js.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Stored Cross-Site Scripting (XSS) in AIL Framework Username Timeline Tooltip","id":"CVE-2026-100176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Ail Framework Crawler: Missing Cookiejar Authorization Check Allows Cross-Organization Cookiejar Attachment","id":"CVE-2026-100177"},"packages":[],"prev":{"headline":"Postie \u003c= 1.9.87 - Unauthenticated Stored Cross-Site Scripting via Email Body URL Autolink","id":"CVE-2026-100175"},"products":["ail framework"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["ail project"]},"summary":"Stored XSS in AIL Framework allows attackers to execute arbitrary JavaScript in an analyst's browser via crafted usernames, leading to session hijacking or data exfiltration.","url":"https://insights.sbomify.com/CVE-2026-100176/"}