2023 CVE Vulnerabilities
31,475 CVEs published in 2023.
| CVE ID | Severity | CVSS | EPSS | Published | Description |
|---|---|---|---|---|---|
| CVE-2023-54388 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54387 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54386 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54385 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54384 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54383 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned. |
| CVE-2023-54382 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54381 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54380 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54379 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54378 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54377 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54376 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-54375 | — | — | — | Aug 6, 2026 | Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE. |
| CVE-2023-45291 | — | — | — | Feb 13, 2026 | Rejected reason: reserved but not needed |
| CVE-2023-6763 | — | — | — | Feb 6, 2026 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2023-32720 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-32719 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-32718 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22944 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22930 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22929 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22928 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22927 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
| CVE-2023-22926 | — | — | — | Jan 22, 2026 | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. The CVE was never used. |
Check if your code is affected by 2023 CVEs
Strix scans your code and infrastructure for known vulnerabilities automatically.
Scan your code now