CVE-2026-100176

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (26th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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., ) 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.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 25, 2026

Advisory Details (1)

Auto-updated Sep 25, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 455dd92c4179 (ail-project/ail-framework)

Fix landed in ail-project/ail-framework commit 455dd92c4179 — awaiting tagged release

https://github.com/ail-project/ail-framework/commit/455dd92c4179c53204368d93681ded4b57e31643

Vendor Advisories for CVE-2026-100176(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 23:20 UTCGHSA enrichment
  3. 2026-10-04 11:33 UTCGHSA enrichment
  4. 2026-10-03 23:47 UTCEG score recompute
  5. 2026-10-03 23:47 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-03 11:58 UTCGHSA enrichment
  8. 2026-10-03 00:11 UTCEG score recompute
  9. 2026-10-03 00:11 UTCGHSA enrichment
  10. 2026-10-02 12:25 UTCGHSA enrichment
  11. 2026-10-02 00:39 UTCEG score recompute
  12. 2026-10-02 00:39 UTCGHSA enrichment
  13. 2026-10-01 19:49 UTCEPSS rescore
  14. 2026-10-01 12:51 UTCGHSA enrichment
  15. 2026-10-01 01:05 UTCEG score recompute
  16. 2026-10-01 01:04 UTCGHSA enrichment
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 13:17 UTCGHSA enrichment
  19. 2026-09-30 01:30 UTCEG score recompute
  20. 2026-09-30 01:30 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 13:44 UTCGHSA enrichment
  23. 2026-09-29 01:50 UTCEG score recompute
  24. 2026-09-29 01:50 UTCGHSA enrichment
  25. 2026-09-28 14:04 UTCEG score recompute
Show 15 more
  1. 2026-09-28 14:04 UTCGHSA enrichment
  2. 2026-09-28 13:50 UTCEPSS rescore
  3. 2026-09-28 02:17 UTCGHSA enrichment
  4. 2026-09-27 14:30 UTCEG score recompute
  5. 2026-09-27 14:30 UTCGHSA enrichment
  6. 2026-09-27 02:44 UTCEG score recompute
  7. 2026-09-27 02:44 UTCGHSA enrichment
  8. 2026-09-26 15:58 UTCEPSS rescore
  9. 2026-09-26 14:57 UTCGHSA enrichment
  10. 2026-09-26 03:10 UTCGHSA enrichment
  11. 2026-09-25 15:23 UTCEG score recompute
  12. 2026-09-25 15:06 UTCEG score recompute
  13. 2026-09-25 14:22 UTCEG score recompute
  14. 2026-09-25 13:36 UTCEG score recompute
  15. 2026-09-25 13:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100176?
CVE-2026-100176 is a high vulnerability published on September 25, 2026. 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…
When was CVE-2026-100176 disclosed?
CVE-2026-100176 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100176 actively exploited?
CVE-2026-100176 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100176?
CVE-2026-100176 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100176?
An upstream fix for CVE-2026-100176 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-100176 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100176

Explore →

Is Your Infrastructure Affected by CVE-2026-100176?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs