2025 CVE Vulnerabilities
45,320 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-34964 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34963 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34962 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34961 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34960 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34959 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34958 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34957 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34956 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34955 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34954 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34953 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34952 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34951 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34950 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34949 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34948 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34947 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34946 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34945 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34944 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34943 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34942 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34941 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34940 | — | — | — | 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