聚合 NVD、CVE 及多源情資，深度解析 RCE 等高危風險。系統整合 CVSS 與 EPSS 模型，動態追蹤 Exploit 資源與 PoC 公開狀態，研判可利用性。結合官方修補與修復方案，優化漏洞管理優先級，縮短回應週期，保障資產安全。
指派機構（CNA / 來源）：[email protected] 移除此篩選
| CVE | 描述 | 最高 CVSS | EPSS % | 公開時間 | 更新時間 |
|---|---|---|---|---|---|
| CVE-2022-44577 | 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.89% | 2022-11-17 | 2023-11-06 |
| CVE-2022-29409 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2024-01-08 | 2024-01-08 |
| CVE-2023-47691 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2024-03-07 | 2024-03-20 |
| CVE-2023-41696 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2024-03-26 | 2024-03-26 |
| CVE-2024-38688 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2024-08-13 | 2024-09-12 |
| CVE-2024-35173 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2024-05-17 | 2025-03-12 |
| CVE-2025-32200 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.04% | 2025-04-04 | 2025-04-14 |
| CVE-2025-22756 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 無 | 2025-05-14 | 2025-05-14 |
| CVE-2025-52709 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.05% | 2025-06-27 | 2025-09-04 |
| CVE-2025-53459 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.03% | 2025-09-22 | 2025-10-22 |
| CVE-2025-57901 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.03% | 2025-09-22 | 2025-11-20 |
| CVE-2025-62908 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.05% | 2025-10-26 | 2025-11-21 |
| CVE-2025-62893 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.02% | 2025-10-26 | 2025-12-08 |
| CVE-2026-0675 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.02% | 2026-01-08 | 2026-01-09 |
| CVE-2024-43275 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Collision with another CVE. | 無 | 0.22% | 2024-08-15 | 2026-02-02 |
| CVE-2024-34764 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Collision with another CVE ID. | 無 | 0.14% | 2024-06-03 | 2026-02-02 |
| CVE-2026-24602 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. This is a false positive. According to the vendor, the function identified as a vulnerability is intentional and part of the expected design. | 無 | 0.01% | 2026-01-23 | 2026-02-04 |
| CVE-2026-25421 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Collision with another CVE. | 無 | 無 | 2026-02-18 | 2026-02-18 |
| CVE-2026-25412 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.02% | 2026-02-19 | 2026-02-24 |
| CVE-2023-47663 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | 無 | 0.18% | 2024-06-04 | 2026-03-18 |