Overview 18,582 matches · 1 in Waratek scope · 1 protected · 7 exploited · 0 CISA KEV · 132 public PoC · 0 EPSS ≥ 0.5
18,582matches
1in Waratek scope0.0%
1protected0.0%
7exploited0.0%
0CISA KEV0.0%
132public PoC0.7%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
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
1,003
5.4%
Withdrawn CVE
17,578
94.6%
blocked by ARMR today
1
0.0%
partly blocked
0
0.0%
not blocked
18,581
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,360
Not applicable2
Withdrawn CVE1,358
Unknown1,360
not blocked1,360
Working exploit published4
Proof of concept only6
No public exploit1,350
20232,134
Not applicable1
Withdrawn CVE2,133
Unknown2,134
not blocked2,134
Exploited1
Working exploit published6
Proof of concept only1
No public exploit2,126
2024759
Protected by Waratek1
Not applicable7
Withdrawn CVE751
Unknown759
blocked by ARMR today1
not blocked758
Exploited1
Working exploit published4
Proof of concept only1
No public exploit753
20252,719
Not applicable897
Withdrawn CVE1,822
Unknown2,719
not blocked2,719
Exploited2
Working exploit published3
Proof of concept only2
No public exploit2,712
20261,274
Not applicable96
Withdrawn CVE1,178
Unknown1,274
not blocked1,274
Exploited1
Proof of concept only1
No public exploit1,272
199319961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-4178 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-34998 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-34997 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-34996 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-34995 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-34994 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2025-51850 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2025-51849 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2025-51847 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2025-13890 | Unknown | 2026-04-30 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-12494. Reason: This candidate is a reservation duplicate of CVE-2025-12494. Notes: All CVE users should reference CVE-2025-12494 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-6221 | Unknown | 2026-04-29 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-5822 | Unknown | 2026-04-28 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-41603 | Unknown | 2026-04-28 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID is Rejected and will not be used. The record incorrectly described the affected language binding and fixed version. Use CVE-2026-66053, which was assigned to the vulnerability. |
| CVE-2026-40556 | Unknown | 2026-04-28 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-6337 | Unknown | 2026-04-27 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-31688 | Unknown | 2026-04-27 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-6175 | Unknown | 2026-04-24 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-40609 | Unknown | 2026-04-24 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE. |
| CVE-2026-31534 | Unknown | 2026-04-24 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-4049 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-35382 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: Voluntarily withdrawn |
| CVE-2014-125120 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2013-10056 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2013-10045 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2013-10041 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2011-10031 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2010-20124 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2010-20118 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2010-20117 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2010-20116 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2010-20110 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2009-20012 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2008-20003 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2008-20002 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2005-20001 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2000-5001 | Unknown | 2026-04-22 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has the been REJECTED and will not be published by the CNA. |
| CVE-2026-4872 | Unknown | 2026-04-21 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-4821 | Unknown | 2026-04-21 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as it was published in error. |
| CVE-2025-70420 | Unknown | 2026-04-21 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-5358 | Unknown | 2026-04-20 | Withdrawn CVE | No public exploit | Rejected reason: REJECTED: CVE-2026-5358 is rejected for two reasons. Firstly it has been discovered that no NIS+ client or server was ever released for any Linux-based OS distributions and as such this makes the API provisional and unused. Secondly it has been discovered that the NIS+ cold start cache (/var/nis/NIS_COLD_START) cannot be bypassed and as such the API can only be called with a trusted server from the pre-populated cache. The use of a trusted server means no trust boundary is crossed and this is therefore considered a normal bug. |
| CVE-2025-11249 | Unknown | 2026-04-20 | Withdrawn CVE | No public exploit | Rejected reason: This CVE id was assigned as a duplicate of CVE-2025-66414. |
| CVE-2026-6056 | Unknown | 2026-04-18 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-5250 | Unknown | 2026-04-17 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-5968 | Unknown | 2026-04-16 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-6398 | Unknown | 2026-04-15 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-40500 | Unknown | 2026-04-15 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. The "Add Module from URL" feature requires superuser privileges (root-equivalent in ProcessWire) who already has unrestricted arbitrary code execution via standard module upload, making the SSRF vector incapable of providing incremental attack surface. The feature is also disabled by default and requires direct filesystem access to enable. |
| CVE-2026-5307 | Unknown | 2026-04-14 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2024-9168 | Unknown | 2026-04-14 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-39398 | Unknown | 2026-04-09 | Withdrawn CVE | No public exploit | Rejected reason: The affected product and advisory are not public. |
| CVE-2026-5904 | Unknown | 2026-04-08 | Withdrawn CVE | No public exploit | Rejected reason: Determined a bug and not a vulnerability |
| CVE-2026-4402 | Unknown | 2026-04-08 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-39660 | Unknown | 2026-04-08 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-39659 | Unknown | 2026-04-08 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-5359 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-4656 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-39323 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39326. Reason: This candidate is a duplicate of CVE-2026-39326. Notes: All CVE users should reference CVE-2026-39326 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.another CVE. |
| CVE-2026-39317 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39334. Reason: This candidate is a duplicate of CVE-2026-39334. Notes: All CVE users should reference CVE-2026-39334 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.another CVE. |
| CVE-2026-3566 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: After further discussion, the issue was determined to not meet the criteria for CVE assignment. |
| CVE-2026-35578 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: This CVE is a duplicate of another CVE.** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39940. Reason: This candidate is a reservation duplicate of CVE-2026-39940. Notes: All CVE users should reference CVE-2026-39940 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-35567 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39327. Reason: This candidate is a duplicate of CVE-2026-39327. Notes: All CVE users should reference CVE-2026-39327 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.another CVE. |
| CVE-2026-35566 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39319. Reason: This candidate is a duplicate of CVE-2026-39319. Notes: All CVE users should reference CVE-2026-39319 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.another CVE. |
| CVE-2026-35481 | Unknown | 2026-04-07 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the issue does not satisfy the assignment rules. |
| CVE-2026-5664 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-30078. Reason: This candidate is a reservation duplicate of CVE-2026-30078. Notes: All CVE users should reference CVE-2026-30078 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-35022 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected by its CVE Numbering Authority (CNA). It was determined that the -p flag behavior is documented in Anthropic's claude -h output with an explicit warning that non-interactive mode should only be used in trusted directories, making this intended and described behavior rather than a vulnerability. |
| CVE-2026-35021 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected by its CVE Numbering Authority (CNA). It was determined that the affected code path cannot be triggered through normal usage of Claude Code. |
| CVE-2026-35020 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected by the its CVE Numbering Authority (CNA). It was determined that the attack requires an attacker to already control arbitrary environment variables, a level of access they consider functionally equivalent to code execution and outside the threat model of CLI tools. |
| CVE-2026-34402 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-39330. Reason: This candidate is a duplicate of CVE-2026-39330. Notes: All CVE users should reference CVE-2026-39330 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.another CVE. |
| CVE-2026-33817 | Unknown | 2026-04-06 | Withdrawn CVE | No public exploit | Rejected reason: CVE confirmed to be a false positive |
| CVE-2019-25685 | Unknown | 2026-04-05 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-31404 | Unknown | 2026-04-03 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-23473 | Unknown | 2026-04-03 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-23471 | Unknown | 2026-04-03 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-4759 | Unknown | 2026-04-01 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-3882 | Unknown | 2026-04-01 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-0711 | Unknown | 2026-04-01 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-34509 | Unknown | 2026-03-31 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-34508 | Unknown | 2026-03-31 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-5128 | Unknown | 2026-03-30 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-4425 | Unknown | 2026-03-30 | Withdrawn CVE | No public exploit | Rejected reason: Reserved for EastLink case, but no need for CVE anymore |
| CVE-2026-4340 | Unknown | 2026-03-27 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-32187 | Unknown | 2026-03-27 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-30407 | Unknown | 2026-03-27 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2026-3126 | Unknown | 2026-03-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-23333 | Unknown | 2026-03-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-23320 | Unknown | 2026-03-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-2535 | Unknown | 2026-03-25 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-3260 | Unknown | 2026-03-24 | Withdrawn CVE | No public exploit | Rejected reason: The Undertow web server enforces a default maximum HTTP request entity size limit. Any request (including GET or HEAD) containing a body that exceeds this configurable limit is safely dropped by the server, preventing single-request Resource Exhaustion (Out of Memory) Denial of Service attacks. |
| CVE-2026-26809 | Unknown | 2026-03-24 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2025-71275 | Unknown | 2026-03-24 | Withdrawn CVE | No public exploit | Rejected reason: This CVE was rejected due to being a duplicate of CVE-2024-45519. |
| CVE-2026-4645 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate of CVE-2026-32287 |
| CVE-2026-32912 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32911 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32910 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32909 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32908 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32907 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32904 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32903 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32902 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |
| CVE-2026-32901 | Unknown | 2026-03-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected. |