NVD や CVE、ほか複数の脅威フィードを束ね、RCE など高リスクな事象を深く追える一覧です。CVSS と EPSS を組み合わせ、Exploit 参照や PoC の有無から悪用しやすさを追跡します。ベンダー修正や緩和策の文脈とあわせて優先度を決め、対応サイクルを短く保ちつつ重要資産を守る支援をします。
Assigner（CNA／発行元）：[email protected] この条件を外す
| CVE | 説明 | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|
| CVE-2021-39324 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none | 該当なし | 0.04% | 2022-09-06 | 2023-11-06 |
| CVE-2021-39326 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none | 該当なし | 0.04% | 2022-09-06 | 2023-11-06 |
| CVE-2021-39330 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2021-24608. Reason: This candidate is a duplicate of CVE-2021-24608. Notes: All CVE users should reference CVE-2021-24608 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage | 該当なし | 0.07% | 2021-10-14 | 2023-11-06 |
| CVE-2021-4342 | Rejected reason: CVE split into individual CVE IDs for each software record. | 該当なし | 0.05% | 2023-06-06 | 2023-11-06 |
| CVE-2022-2445 | Rejected reason: Incorrectly assigned CVE. Not a valid issue. | 該当なし | 0.04% | 2023-04-13 | 2023-11-06 |
| CVE-2022-3403 | Rejected reason: Duplicate, please use CVE-2023-28931 instead. | 該当なし | 0.04% | 2023-08-11 | 2023-11-06 |
| CVE-2022-3404 | Rejected reason: This candidate is unused by its CNA. | 該当なし | 0.04% | 2023-04-12 | 2023-11-06 |
| CVE-2022-4367 | Rejected reason: Duplicate, use CVE-2023-4279 instead. | 該当なし | 0.04% | 2023-08-21 | 2023-11-06 |
| CVE-2022-4463 | Rejected reason: This candidate is unused by its CNA. | 該当なし | 0.04% | 2023-04-12 | 2023-11-06 |
| CVE-2022-4531 | Rejected reason: Not a valid vulnerability. | 該当なし | 0.04% | 2023-10-19 | 2023-11-06 |
| CVE-2023-0039 | Rejected reason: Duplicate. Please use CVE-2022-4060 instead. | 該当なし | 0.06% | 2023-01-03 | 2023-11-06 |
| CVE-2023-1271 | Rejected reason: Duplicate. Please use CVE-2023-24421. | 該当なし | 0.04% | 2023-04-13 | 2023-11-06 |
| CVE-2023-1706 | Rejected reason: This candidate is unused by its CNA. | 該当なし | 0.04% | 2023-04-12 | 2023-11-06 |
| CVE-2023-2230 | Rejected reason: Accidental Assignment | 該当なし | 0.04% | 2023-08-08 | 2023-11-06 |
| CVE-2023-2918 | Rejected reason: Duplicate Assignment. | 該当なし | 0.04% | 2023-06-16 | 2023-11-06 |
| CVE-2023-2994 | Rejected reason: This 2023 CVE was incorrectly assigned instead of a 2022 CVE. | 該当なし | 0.04% | 2023-05-30 | 2023-11-06 |
| CVE-2023-3123 | Rejected reason: Duplicate Assignment. | 該当なし | 0.04% | 2023-06-06 | 2023-11-06 |
| CVE-2023-3351 | Rejected reason: Wrong year requested. | 該当なし | 0.04% | 2023-06-21 | 2023-11-06 |
| CVE-2023-3451 | Rejected reason: Duplicate CVE. Please use CVE-2023-32297. | 該当なし | 0.04% | 2023-07-26 | 2023-11-06 |
| CVE-2023-4026 | Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-4024. Reason: This record is a duplicate of CVE-2023-4024. Notes: All CVE users should reference CVE-2023-4024 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. | 該当なし | 該当なし | 2023-07-31 | 2023-11-06 |