CVE Program Container

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

   Jul 7, 2021

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

2. Source modified

   Sep 16, 2026

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

3. First seen by HOL

   Sep 16, 2026

Sources and claim methodology

• Source referenceseclists.org
• Source referencemikrotik.com
• Source referenceseclists.org
• Source referenceseclists.org

Related CVEs

• djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization capability (session hijack)Same generic ecosystem
• djust is vulnerable to stored/reflected XSS via javascript: URLs in built-in component template tagsSame generic ecosystem
• Kedro-Datasets: Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load`Same generic ecosystem
• RMCP: Custom HTTP headers leak to cross-origin redirect targetsSame generic ecosystem
• Marten: SQL injection in Marten's LINQ provider via unescaped string literalsSame generic ecosystem
• OpenTelemetry-Go: UTF-8 replacement rune bypasses attribute length truncationSame generic ecosystem