| CVE-2026-56860 | |
| GHSA-xphw-4f88-5f39 | |
| CVE-2026-33818 | |
| GHSA-w2q5-6q6x-x959 | |
| CVE-2026-56853 | |
| CVE-2026-39821 | |
| GHSA-xc2p-8ggw-6cr5 | |
| GHSA-25mv-j2qr-v5jq | |
| GHSA-7qch-w8m5-g3h3 | |
| CVE-2026-56862 | |
| GHSA-ff52-ph69-cf7x | |
| CVE-2026-42505 | |
| GHSA-qf3q-3h68-mmh2 | |
| GHSA-qc64-m6c2-v4x7 | |
| NULL Pointer Dereference | |
| CVE-2026-42501 | |
| GHSA-8g2r-hhvj-mv99 | |
| GHSA-5m4p-2gjx-p2g8 | |
| Link Following | |
| Out-of-bounds Write | |
| Loop with Unreachable Exit Condition ('Infinite Loop') | |
| Improper Certificate Validation | |
| GHSA-5w89-2c2x-6x66 | |
| GHSA-gjvh-7jh8-7xhm | |
| GHSA-m4pr-4j3g-9v7v | |
| CVE-2026-32280 | |
| GHSA-x4jj-h2v8-hqqv | |
| GHSA-jrg3-gfjw-hm96 | |
| Allocation of Resources Without Limits or Throttling | |
| Incorrect Authorization | |
| Allocation of Resources Without Limits or Throttling | |
| Directory Traversal | |
| Direct Request ('Forced Browsing') | |
| GHSA-j3gx-2473-5fp8 | |
| GHSA-rv83-g57w-fr8j | |
| GHSA-h355-32pf-p2xm | |
| GHSA-8jvr-vh7g-f8gx | |
| CVE-2025-68121 | |
| CVE-2025-61732 | |
| Algorithmic Complexity | |
| CVE-2025-61725 | |
| Improper Certificate Validation | |
| CVE-2025-58186 | |
| CVE-2025-47912 | |
| Allocation of Resources Without Limits or Throttling | |
| CVE-2025-58183 | |
| Allocation of Resources Without Limits or Throttling | |
| Information Exposure Through Log Files | |
| Allocation of Resources Without Limits or Throttling | |
| CVE-2025-22871 | |
| CVE-2025-22866 | |
| CVE-2024-45336 | |
| CVE-2024-45341 | |
| CVE-2024-34158 | |
| CVE-2024-34155 | |
| CVE-2024-34156 | |
| CVE-2024-24791 | |
| CVE-2024-24790 | |
| CVE-2024-24789 | |
| CVE-2024-24788 | |
| CVE-2024-24787 | |
| CVE-2023-45288 | |
| Origin Validation Error | |