聚合 NVD、CVE 及多源情資，深度解析 RCE 等高危風險。系統整合 CVSS 與 EPSS 模型，動態追蹤 Exploit 資源與 PoC 公開狀態，研判可利用性。結合官方修補與修復方案，優化漏洞管理優先級，縮短回應週期，保障資產安全。
指派機構（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 |