Overview 8,841 matches · 0 in Waratek scope · 0 protected · 5 exploited · 0 CISA KEV · 29 public PoC · 0 EPSS ≥ 0.5
8,841matches
0in Waratek scope0.0%
0protected0.0%
5exploited0.1%
0CISA KEV0.0%
29public PoC0.3%
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
8,841
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
8,841
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 1,103 / quarter
Q1 22300
Withdrawn CVE300
Unknown300
not blocked300
Proof of concept only1
No public exploit299
Q2 2283
Withdrawn CVE83
Unknown83
not blocked83
Working exploit published4
Proof of concept only2
No public exploit77
Q3 22405
Withdrawn CVE405
Unknown405
not blocked405
Proof of concept only1
No public exploit404
Q4 22570
Withdrawn CVE570
Unknown570
not blocked570
Proof of concept only2
No public exploit568
Q1 23847
Withdrawn CVE847
Unknown847
not blocked847
Working exploit published1
No public exploit846
Q2 23370
Withdrawn CVE370
Unknown370
not blocked370
Exploited1
Working exploit published1
No public exploit368
Q3 23779
Withdrawn CVE779
Unknown779
not blocked779
Working exploit published4
Proof of concept only1
No public exploit774
Q4 23137
Withdrawn CVE137
Unknown137
not blocked137
No public exploit137
Q1 24224
Withdrawn CVE224
Unknown224
not blocked224
Working exploit published2
No public exploit222
Q2 24313
Withdrawn CVE313
Unknown313
not blocked313
Working exploit published1
No public exploit312
Q3 24136
Withdrawn CVE136
Unknown136
not blocked136
Working exploit published1
No public exploit135
Q4 2478
Withdrawn CVE78
Unknown78
not blocked78
No public exploit78
Q1 25466
Withdrawn CVE466
Unknown466
not blocked466
Exploited2
Working exploit published1
Proof of concept only1
No public exploit462
Q2 25510
Withdrawn CVE510
Unknown510
not blocked510
No public exploit510
Q3 25482
Withdrawn CVE482
Unknown482
not blocked482
Proof of concept only1
No public exploit481
Q4 25364
Withdrawn CVE364
Unknown364
not blocked364
Working exploit published2
No public exploit362
Q1 261,103
Withdrawn CVE1,103
Unknown1,103
not blocked1,103
Exploited1
Proof of concept only1
No public exploit1,101
Q2 26183
Withdrawn CVE183
Unknown183
not blocked183
No public exploit183
Q3 26760
Withdrawn CVE760
Unknown760
not blocked760
No public exploit760
Q4 26731
Withdrawn CVE731
Unknown731
not blocked731
Exploited1
No public exploit730
Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-130586 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | |
| CVE-2026-130585 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | |
| 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 |
| CVE-2022-44526 | 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-44525 | 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-44524 | 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-44523 | 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-44522 | 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-44521 | 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-44511 | 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 |