NVD や CVE、ほか複数の脅威フィードを束ね、RCE など高リスクな事象を深く追える一覧です。CVSS と EPSS を組み合わせ、Exploit 参照や PoC の有無から悪用しやすさを追跡します。ベンダー修正や緩和策の文脈とあわせて優先度を決め、対応サイクルを短く保ちつつ重要資産を守る支援をします。
Assigner（CNA／発行元）：[email protected] この条件を外す
| CVE | 説明 | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|
| CVE-2020-8451 | Rejected reason: The reserved CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8452 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8453 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8454 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8455 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8456 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8457 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8458 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8459 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2020-8460 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2021-26253 | A potential vulnerability in Splunk Enterprise's implementation of DUO MFA allows for bypassing the MFA verification in Splunk Enterprise versions before 8.1.6. The potential vulnerability impacts Splunk Enterprise instances configured to use DUO MFA and does not impact or affect a DUO product or service. | 8.1 | 0.75% | 2022-05-06 | 2026-06-16 |
| CVE-2021-31559 | A crafted request bypasses S2S TCP Token authentication writing arbitrary events to an index in Splunk Enterprise Indexer 8.1 versions before 8.1.5 and 8.2 versions before 8.2.1. The vulnerability impacts Indexers configured to use TCPTokens. It does not impact Universal Forwarders. | 7.5 | 0.81% | 2022-05-06 | 2026-06-16 |
| CVE-2021-33845 | The Splunk Enterprise REST API allows enumeration of usernames via the lockout error message. The potential vulnerability impacts Splunk Enterprise instances before 8.1.7 when configured to repress verbose login errors. | 5.3 | 0.78% | 2022-05-06 | 2026-06-16 |
| CVE-2021-3422 | The lack of validation of a key-value field in the Splunk-to-Splunk protocol results in a denial-of-service in Splunk Enterprise instances configured to index Universal Forwarder traffic. The vulnerability impacts Splunk Enterprise versions before 7.3.9, 8.0 versions before 8.0.9, and 8.1 versions before 8.1.3. It does not impact Universal Forwarders. When Splunk forwarding is secured using TLS or a Token, the attack requires compromising the certificate or token, or both. Implementation of eith | 7.5 | 0.58% | 2022-03-25 | 2026-06-17 |
| CVE-2021-3926 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2021-42743 | A misconfiguration in the node default path allows for local privilege escalation from a lower privileged user to the Splunk user in Splunk Enterprise versions before 8.1.1 on Windows. | 8.8 | 0.22% | 2022-05-06 | 2026-06-17 |
| CVE-2022-21130 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2022-22147 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2022-24380 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |
| CVE-2022-24911 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. | 該当なし | 該当なし | 2026-01-22 | 2026-01-22 |