Overview 1,349 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
1,349matches
0in Waratek scope0.0%
0protected0.0%
1exploited0.1%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
0
0.0%
Withdrawn CVE
1,349
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
1,349
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
0.1%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
1,348
99.9%
split by
peak 464 / month
Aug 26464
Withdrawn CVE464
Unknown464
not blocked464
No public exploit464
Sep 26147
Withdrawn CVE147
Unknown147
not blocked147
No public exploit147
Oct 26430
Withdrawn CVE430
Unknown430
not blocked430
Exploited1
No public exploit429
Nov 26308
Withdrawn CVE308
Unknown308
not blocked308
No public exploit308
Aug 26Sep 26Oct 26Nov 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-59912 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59911 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59910 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59909 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59908 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59907 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2025-59906 | Unknown | 2026-11-18 | Withdrawn CVE | No public exploit | |
| CVE-2026-130586 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-130585 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-71512 | Unknown | 2026-11-16 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-65683 | Unknown | 2026-11-16 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-43626 | Unknown | 2026-11-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority, replacedby CVE-2026-70640. |
| CVE-2026-128133 | Unknown | 2026-11-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2026-82032 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-70641 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as a duplicate of CVE-2026-82873. |
| CVE-2026-125324 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2026-124617 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: 歸類為 JSONCPP Open Source 之問題 |
| CVE-2026-123133 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID is a duplicate of CVE-2026-116518 and was never published. Both IDs were assigned to the same vulnerability in the ElasticPress WordPress plugin. All CVE users should reference CVE-2026-116518 instead of this ID. |
| CVE-2026-117476 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This is rejected. |
| CVE-2026-117475 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This is rejected. |
| CVE-2026-117474 | Unknown | 2026-11-12 | Withdrawn CVE | No public exploit | Rejected reason: This is rejected. |
| CVE-2026-107922 | Unknown | 2026-11-11 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-59599 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-126082 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2026-125346 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate CVE. Replaced by CVE-2026-125350 |
| CVE-2026-123439 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123438 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123437 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123435 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123432 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123431 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123430 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123429 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123427 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123426 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123425 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-123424 | Unknown | 2026-11-10 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected as a duplicate. |
| CVE-2026-124610 | Unknown | 2026-11-09 | Withdrawn CVE | No public exploit | Rejected reason: 依 VUL-2026-008441 判定為主 |
| CVE-2026-73860 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-18107. Reason: This candidate is a duplicate of CVE-2026-18107. Notes: All CVE users should reference CVE-2026-18107 instead of this candidate. |
| CVE-2026-56717 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-49126 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-49125 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-49124 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-49123 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-49122 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-47404 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-47403 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-47402 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-47401 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-47400 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-120484 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-119167 Reason: This candidate is a reservation duplicate of CVE-2026-119167. Notes: All CVE users should reference CVE-2026-119167 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-119217 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate is a reservation duplicate. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-107931 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-107492 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-10147 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-10146 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-64798 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: Unused reservation with no CVE record; removed from tickets/pool during the 2026-11-06 stale-CVE remediation |
| CVE-2025-46896 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: Unused reservation with no CVE record; removed from tickets/pool during the 2026-11-06 stale-CVE remediation |
| CVE-2024-36240 | Unknown | 2026-11-06 | Withdrawn CVE | No public exploit | Rejected reason: Unused reservation with no CVE record; removed from tickets/pool during the 2026-11-06 stale-CVE remediation |
| CVE-2026-69143 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2026-16579 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2023-51466 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-51465 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47089 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47088 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47087 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47086 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47085 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47084 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47083 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47082 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-47045 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44370 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44369 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44368 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44364 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44363 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44354 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-44349 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-38202 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-29493 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-26399 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-26365 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-26363 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-26362 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-26357 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-22270 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-22267 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-22255 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-22245 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-21623 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-21617 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-21602 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-21600 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2023-21580 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2022-44531 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2022-44530 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2022-44529 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2022-44528 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |
| CVE-2022-44527 | Unknown | 2026-11-05 | Withdrawn CVE | No public exploit | Rejected reason: Reserved ID never published and not linked to any VULN ticket - quota reclaim 2026-11-05 |