2025 CVE Vulnerabilities
45,150 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-34488 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34487 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34486 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34485 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34484 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34483 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34482 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34481 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34480 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34479 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34478 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34477 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34476 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34475 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34474 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34473 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34472 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34471 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34470 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34466 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34465 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34464 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34463 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34462 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34461 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
Check if your code is affected by 2025 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now