2025 CVE Vulnerabilities
45,522 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-34094 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-15427 | — | — | — | Jan 2, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn b... |
| CVE-2025-22203 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22202 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22201 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22200 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22199 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22198 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22197 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22196 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22195 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22194 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22193 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22192 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22191 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22190 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22189 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22188 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22187 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22186 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22185 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22184 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22183 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22182 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
| CVE-2025-22181 | — | — | — | Jan 1, 2026 | Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used. |
Check if your code is affected by 2025 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now