CISA ADP Vulnrichment

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps n/a/n/a (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for n/a/n/a.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 18, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 18, 2026

Sources and claim methodology

• Source referencekimi.com
• Source referencemoonshot.com
• GitHub security advisorygithub.com
• Source referencekimi.com

Related CVEs

• Semantic MediaWiki affected by reflected XSS in `Special:Ask` via a forged cursor pagination tokenAlso CWE-79
• md-editor-v3: XSS via fenced-code language rendering bypassAlso CWE-79
• File Viewer: DOM XSS via unsafe hyperlink schemes in the legacy DOC rendererAlso CWE-79
• Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkusAlso CWE-79
• LMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pySame generic ecosystem
• Parseable: Unauthenticated Denial of Service via panic in Kinesis header parsing middlewareSame generic ecosystem