Overview 15,711 matches · 0 in Waratek scope · 0 protected · 5 exploited · 0 CISA KEV · 128 public PoC · 0 EPSS ≥ 0.5
15,711matches
0in Waratek scope0.0%
0protected0.0%
5exploited0.0%
0CISA KEV0.0%
128public PoC0.8%
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
15,711
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
15,711
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 3,471 / year
19921
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19930
19941
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19950
19961
Withdrawn CVE1
Unknown1
not blocked1
Working exploit published1
19971
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19981
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
199929
Withdrawn CVE29
Unknown29
not blocked29
Working exploit published1
No public exploit28
20001
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
20013
Withdrawn CVE3
Unknown3
not blocked3
No public exploit3
200214
Withdrawn CVE14
Unknown14
not blocked14
Working exploit published2
No public exploit12
200321
Withdrawn CVE21
Unknown21
not blocked21
Working exploit published1
No public exploit20
200428
Withdrawn CVE28
Unknown28
not blocked28
No public exploit28
200578
Withdrawn CVE78
Unknown78
not blocked78
Working exploit published5
No public exploit73
200651
Withdrawn CVE51
Unknown51
not blocked51
Working exploit published3
No public exploit48
200780
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published3
No public exploit77
200832
Withdrawn CVE32
Unknown32
not blocked32
Working exploit published5
No public exploit27
200946
Withdrawn CVE46
Unknown46
not blocked46
Working exploit published6
No public exploit40
201028
Withdrawn CVE28
Unknown28
not blocked28
Working exploit published2
No public exploit26
201122
Withdrawn CVE22
Unknown22
not blocked22
Working exploit published3
No public exploit19
201263
Withdrawn CVE63
Unknown63
not blocked63
Working exploit published5
No public exploit58
2013137
Withdrawn CVE137
Unknown137
not blocked137
Working exploit published20
No public exploit117
201480
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published11
No public exploit69
2015101
Withdrawn CVE101
Unknown101
not blocked101
Working exploit published5
No public exploit96
201668
Withdrawn CVE68
Unknown68
not blocked68
Working exploit published4
No public exploit64
20173,471
Withdrawn CVE3,471
Unknown3,471
not blocked3,471
Exploited1
Working exploit published10
No public exploit3,460
20181,644
Withdrawn CVE1,644
Unknown1,644
not blocked1,644
Working exploit published5
Proof of concept only1
No public exploit1,638
20191,633
Withdrawn CVE1,633
Unknown1,633
not blocked1,633
Exploited1
Working exploit published3
No public exploit1,629
2020900
Withdrawn CVE900
Unknown900
not blocked900
Working exploit published5
No public exploit895
20211,801
Withdrawn CVE1,801
Unknown1,801
not blocked1,801
Working exploit published1
No public exploit1,800
20221,358
Withdrawn CVE1,358
Unknown1,358
not blocked1,358
Working exploit published4
Proof of concept only6
No public exploit1,348
20232,133
Withdrawn CVE2,133
Unknown2,133
not blocked2,133
Exploited1
Working exploit published6
Proof of concept only1
No public exploit2,125
2024751
Withdrawn CVE751
Unknown751
not blocked751
Working exploit published4
No public exploit747
20251,133
Withdrawn CVE1,133
Unknown1,133
not blocked1,133
Exploited2
Working exploit published1
Proof of concept only2
No public exploit1,128
199219951998200120042007201020132016201920222025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-54829 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54828 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54827 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54826 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54825 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54824 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54823 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2023-41674 | Unknown | 2025-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-7356 | Unknown | 2025-07-30 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-54582 | Unknown | 2025-07-30 | Withdrawn CVE | No public exploit | Rejected reason: Reason: This candidate was issued in error. Valid Netty requests are issued via https://github.com/netty/netty. |
| CVE-2024-11478 | Unknown | 2025-07-30 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-54666 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54665 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54664 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54663 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54662 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54661 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54432 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. See CVE-2018-25031 and CVE-2021-46708. |
| CVE-2025-54420 | Unknown | 2025-07-29 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of CVE-2025-8129. |
| CVE-2025-8263 | Unknown | 2025-07-28 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2023-2274 | Unknown | 2025-07-26 | Withdrawn CVE | No public exploit | Rejected reason: This CVE assignment was considered invalid after investigation. |
| CVE-2025-8197 | Unknown | 2025-07-25 | Withdrawn CVE | No public exploit | Rejected reason: Maintainers have included reasons at https://gitlab.gnome.org/GNOME/libsoup/-/issues/465 |
| CVE-2025-38380 | Unknown | 2025-07-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-34138 | Unknown | 2025-07-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority, as it is a duplicate of CVE-2025-53692 and CVE-2025-53694. |
| CVE-2025-29630 | Unknown | 2025-07-25 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue; there is no indication that an applicable SSH private key has ever been compromised. Notes: none. |
| CVE-2025-8022 | Unknown | 2025-07-23 | Withdrawn CVE | No public exploit | Rejected reason: Bun Shell does not invoke /bin/sh, or any other interpreter, for template literals created with the $ function. Each ${…} interpolation is treated as a single argument. The security responsibility for this usage pattern lies with the calling application, which must ensure the sanitization and validation of any untrusted arguments before passing them to the executed commands. Therefore, the potential for command injection is not a flaw within Bun itself; rather, it is an argument injection that is contingent on its implementation by the consuming application. |
| CVE-2025-54371 | Unknown | 2025-07-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2025-54362 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54361 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54360 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54359 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54358 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54357 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54356 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54355 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-54354 | Unknown | 2025-07-22 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-29572 | Unknown | 2025-07-18 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-52933 | Unknown | 2025-07-17 | Withdrawn CVE | No public exploit | Rejected reason: 3rd party vulnerability |
| CVE-2025-53958 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53957 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53956 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53955 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53954 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53953 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53952 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2024-12498 | Unknown | 2025-07-16 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-53879 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53878 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53877 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53876 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53875 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53874 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53873 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53872 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53871 | Unknown | 2025-07-12 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53852 | Unknown | 2025-07-11 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53851 | Unknown | 2025-07-11 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53850 | Unknown | 2025-07-11 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53849 | Unknown | 2025-07-11 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53848 | Unknown | 2025-07-11 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-7370 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Upon investigtion upstream maintainers discovered this was not a real issue. See the references for more details. See: https://gitlab.gnome.org/GNOME/libsoup/-/issues/430#note_2494090. |
| CVE-2025-53753 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53752 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53751 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53750 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53749 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53748 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53747 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53746 | Unknown | 2025-07-10 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53688 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53687 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53686 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53685 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53684 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53683 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53682 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-34085 | Unknown | 2025-07-09 | Withdrawn CVE | Proof of concept only | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36847. |
| CVE-2025-34084 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36848. |
| CVE-2025-34083 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it is a duplicate of CVE-2020-36849. |
| CVE-2025-0646 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2024-10391 | Unknown | 2025-07-09 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-53617 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53616 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53615 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53614 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53613 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53612 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53611 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-53610 | Unknown | 2025-07-08 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-6022 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-5316 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-5104 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-4950 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-4694 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-3896 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-3524 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-3283 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-3156 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-3094 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-2904 | Unknown | 2025-07-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |