2025 CVE Vulnerabilities
45,320 CVEs published in 2025.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2025-34383 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34382 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34381 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34380 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34379 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34378 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34377 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34376 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34375 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34374 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34373 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34372 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34371 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34370 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34369 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34368 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34367 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34366 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34365 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34364 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34363 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34362 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34361 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34360 | — | — | — | Jan 2, 2026 | Rejected reason: This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. |
| CVE-2025-34359 | — | — | — | 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