Total
396909 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2025-12200 | 2025-11-03 | N/A | N/A | ||
| Rejected reason: ** REJECT ** 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: Based on the analysis by MITRE and review of community feedback, the reported conditions represent expected and intentional behavior within dnsmasq's documented design, rather than security vulnerabilities. | |||||
| CVE-2025-12199 | 2025-11-03 | N/A | N/A | ||
| Rejected reason: ** REJECT ** 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: Based on the analysis by MITRE and review of community feedback, the reported conditions represent expected and intentional behavior within dnsmasq's documented design, rather than security vulnerabilities. | |||||
| CVE-2025-12198 | 2025-11-03 | N/A | N/A | ||
| Rejected reason: ** REJECT ** 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: Based on the analysis by MITRE and review of community feedback, the reported conditions represent expected and intentional behavior within dnsmasq's documented design, rather than security vulnerabilities. | |||||
| CVE-2025-45959 | 2025-11-03 | N/A | N/A | ||
| Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | |||||
| CVE-2021-47692 | 2025-10-31 | N/A | N/A | ||
| 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 . | |||||
| CVE-2025-11569 | 2025-10-30 | N/A | N/A | ||
| Rejected reason: This record was withdrawn by its CNA; further investigation revealed it was not a security issue. | |||||
| CVE-2025-11428 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-62516 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Further research determined the issue is not a vulnerability. | |||||
| CVE-2025-35980 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: ** REJECT ** 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 2025. Notes: none. | |||||
| CVE-2023-39178 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Duplicate of CVE-2023-52441. | |||||
| CVE-2023-39177 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Duplicate of CVE-2023-52442. | |||||
| CVE-2023-53293 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-62813 | 2025-10-29 | N/A | N/A | ||
| 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. | |||||
| CVE-2025-64162 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-64161 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-64160 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-64159 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-64158 | 2025-10-29 | N/A | N/A | ||
| Rejected reason: Not used | |||||
| CVE-2025-39898 | 2025-10-24 | N/A | N/A | ||
| Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | |||||
| CVE-2025-62835 | 2025-10-24 | N/A | N/A | ||
| Rejected reason: Not used | |||||