2025 CVE Vulnerabilities
45,522 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-34620 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34619 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34618 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34617 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34616 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34615 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34614 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34613 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34612 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34611 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34610 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34609 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34608 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34607 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34606 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34605 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34604 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34603 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34602 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34601 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34600 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34599 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34598 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34597 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34596 | — | — | — | 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