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

   Dec 20, 2023

   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 referencebalwurk.github.io
• Source referenceghostline.neocities.org

Related CVEs

• Kedro-Datasets: Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load`Same 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
• OpenTelemetry-Go: Log gRPC exporter ignores env TLS certs, bypassing mTLS/pinningSame generic ecosystem
• OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is fullSame generic ecosystem
• Pelican Panel before 1.0.0-beta35 Authorization Bypass via StartupSame generic ecosystem