Aggregating NVD, CVE, and multi-source threat feeds, this list provides deep analysis of high-risk threats such as RCE. By integrating CVSS and EPSS models, the system dynamically tracks Exp (Exploit) resources and PoC availability to accurately assess Exploitability. Combined with official Patches and remediation strategies, it helps prioritize Vulnerability Management workflows, significantly shortening response cycles and securing your critical assets.
Assigner (CNA / source)：[email protected] Remove this filter
| CVE | Description | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|
| CVE-2025-2778 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | N/A | N/A | 2025-05-07 | 2025-05-07 |
| CVE-2025-34075 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Initially assigned to document an issues that allows guest VM to modify the host’s Vagrantfile via default synced folder, leading to host-side code execution. Rejected as CVE due to documented, intended behavior that does not violate a claimed security boundary. https://developer.hashicorp.com/vagrant/docs/synced-folders | N/A | 0.02% | 2025-07-02 | 2025-07-16 |
| CVE-2025-34083 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36849. | N/A | 0.26% | 2025-07-08 | 2025-07-16 |
| CVE-2025-34084 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36848. | N/A | 0.27% | 2025-07-08 | 2025-07-16 |
| CVE-2025-34085 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36847. | N/A | 0.61% | 2025-07-08 | 2025-07-16 |
| CVE-2025-34052 | Rejected reason: An unauthenticated endpoint that exposes firmware version, MAC address, and supported codecs is not indicative of a security boundary being crossed, as this metadata is not inherently sensitive and commonly used for legitimate fingerprinting and discovery. | N/A | 0.13% | 2025-07-01 | 2025-10-09 |
| CVE-2025-34252 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. This vulnerability has been reassigned as CVE-2017-20203 ( https://www.cve.org/CVERecord?id=CVE-2017-20203 ) to have the year of the CVE correspond to the year of public disclosure. | N/A | 0.33% | 2025-10-07 | 2025-10-09 |
| CVE-2021-47692 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. It has been identified as a duplicate of https://www.cve.org/CVERecord?id=CVE-2021-33179 . | N/A | 0.30% | 2025-10-30 | 2025-10-31 |
| CVE-2025-34249 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2025-60425. | N/A | 1.56% | 2025-10-30 | 2025-11-07 |
| CVE-2025-34269 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2025-60424. | N/A | 0.29% | 2025-10-30 | 2025-11-07 |
| CVE-2016-15054 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a downstream effect of an already identified vulnerability, CVE-2012-6708. | N/A | 0.37% | 2025-11-03 | 2025-11-10 |
| CVE-2024-58272 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2023-7323. | N/A | 0.13% | 2025-10-30 | 2025-11-10 |
| CVE-2025-34138 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority, as it is a duplicate of CVE-2025-53692 and CVE-2025-53694. | N/A | 0.64% | 2025-07-25 | 2025-12-04 |
| CVE-2025-34351 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022). | N/A | 0.47% | 2025-11-26 | 2025-12-09 |
| CVE-2025-34294 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as the behavior originates from a documentation-published Active Response example script. Please refer to this advisory ( https://github.com/wazuh/wazuh-documentation/security/advisories/GHSA-46r5-xp98-fpgg ) for further information. | N/A | 0.01% | 2025-10-28 | 2025-12-19 |
| CVE-2025-34411 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it identified a vulnerability in a SaaS product that does not require user action. | N/A | 0.10% | 2025-12-15 | 2025-12-24 |
| CVE-2025-34412 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it identified a vulnerability in a SaaS product that does not require user action. | N/A | 0.06% | 2025-12-15 | 2025-12-24 |
| CVE-2018-25153 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as the reported issue does not constitute a security vulnerability and represents a minor, non-exploitable memory leak. | N/A | 0.03% | 2025-12-24 | 2025-12-29 |
| CVE-2025-34094 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | N/A | N/A | 2026-01-02 | 2026-01-02 |
| CVE-2025-34122 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | N/A | N/A | 2026-01-02 | 2026-01-02 |