NVD や CVE、ほか複数の脅威フィードを束ね、RCE など高リスクな事象を深く追える一覧です。CVSS と EPSS を組み合わせ、Exploit 参照や PoC の有無から悪用しやすさを追跡します。ベンダー修正や緩和策の文脈とあわせて優先度を決め、対応サイクルを短く保ちつつ重要資産を守る支援をします。
Assigner（CNA／発行元）：[email protected] この条件を外す
| CVE | 説明 | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|
| CVE-2021-20015 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20014 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20013 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20012 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20011 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20010 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20009 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20008 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20007 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20006 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20005 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20004 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20003 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2021-20002 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2021. Notes: none | 該当なし | 0.04% | 2022-02-09 | 2023-11-06 |
| CVE-2015-0849 | pycode-browser before version 1.0 is prone to a predictable temporary file vulnerability. | 3.9 | 0.11% | 2025-06-26 | 2026-06-16 |
| CVE-2014-6274 | git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes was set, and the remote used encryption=pubkey or encryption=hybrid, the embedded AWS credentials were stored in the git repository in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919. | 7.5 | 0.15% | 2025-06-26 | 2026-06-16 |
| CVE-2012-2266 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2012. Notes: none | 該当なし | 0.17% | 2013-10-09 | 2023-11-06 |
| CVE-2012-2265 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2012. Notes: none | 該当なし | 0.17% | 2013-10-09 | 2023-11-06 |
| CVE-2012-2264 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2012. Notes: none | 該当なし | 0.17% | 2013-10-09 | 2023-11-06 |
| CVE-2012-2263 | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2012. Notes: none | 該当なし | 0.17% | 2013-10-09 | 2023-11-06 |