Overview 13 matches · 1 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 12 public PoC · 0 EPSS ≥ 0.5
13matches
1in Waratek scope7.7%
1protected7.7%
0exploited0.0%
0CISA KEV0.0%
12public PoC92.3%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
7.7%
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
7.7%
Withdrawn CVE
11
84.6%
blocked by ARMR today
1
7.7%
partly blocked
0
0.0%
not blocked
12
92.3%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
13
100.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 6 / year
20181
Withdrawn CVE1
Unknown1
not blocked1
Proof of concept only1
20190
20200
20210
20226
Withdrawn CVE6
Unknown6
not blocked6
Proof of concept only6
20231
Withdrawn CVE1
Unknown1
not blocked1
Proof of concept only1
20241
Protected by Waratek1
Unknown1
blocked by ARMR today1
Proof of concept only1
20252
Withdrawn CVE2
Unknown2
not blocked2
Proof of concept only2
20262
Not applicable1
Withdrawn CVE1
Unknown2
not blocked2
Proof of concept only2
201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-98937 | Unknown | 2026-10-23 | Not applicable | Proof of concept only | In the Linux kernel, the following vulnerability has been resolved: perf/core: Check kernel access when kernel callchains are requested perf_event_open() currently gates perf_allow_kernel() only on !attr.exclude_kernel. However, users can still request kernel callchain collection with attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1. That still requires kernel profiling privilege, but the existing check does not enforce it. Update the permission check to call perf_allow_kernel() when either kernel sampling is requested or kernel callchains are requested. This keeps permission checks aligned with requested data and prevents unprivileged use of kernel callchain capture. |
| CVE-2026-0866 | Unknown | 2026-03-18 | Withdrawn CVE | Proof of concept only | Rejected reason: After the publication of the PoC by the researcher and further analysis, we have determined that this issue does not constitute a valid vulnerability. The technique described is an obfuscation method and does not bypass or impact any implicit or explicit security controls. |
| 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-2022-20128 | Unknown | 2025-01-17 | Withdrawn CVE | Proof of concept only | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2024-49203 | Unknown | 2024-11-20 | Protected by Waratek | Proof of concept only | Querydsl 5.1.0 and OpenFeign Querydsl 6.8 allows SQL/HQL injection in orderBy in JPAQuery. NOTE: this is disputed by a Querydsl community member because the product is not intended to defend against a developer who uses untrusted input directly in query construction. |
| CVE-2023-36168 | Unknown | 2023-07-15 | Withdrawn CVE | Proof of concept only | 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. Notes: none. |
| CVE-2022-44721 | Unknown | 2022-12-04 | Withdrawn CVE | Proof of concept only | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-2841. Reason: This issue was MERGED into CVE-2022-2841 in accordance with CVE content decisions, because it is the same type of vulnerability and affects the same versions. Notes: All CVE users should reference CVE-2022-2841 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2022-41852 | Unknown | 2022-10-06 | Withdrawn CVE | Proof of concept only | 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. Notes: none. |
| CVE-2022-1972 | Unknown | 2022-09-14 | Withdrawn CVE | Proof of concept only | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2022-2078. Reason: This candidate is a reservation duplicate of CVE-2022-2078. Notes: All CVE users should reference CVE-2022-2078 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage |
| CVE-2022-30778 | Unknown | 2022-05-16 | Withdrawn CVE | Proof of concept only | 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. Notes: none |
| CVE-2021-43503 | Unknown | 2022-04-08 | Withdrawn CVE | Proof of concept only | 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. Notes: none |
| CVE-2022-23967 | Unknown | 2022-01-26 | Withdrawn CVE | Proof of concept only | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-15679. Reason: This candidate is a duplicate of CVE-2019-15679. Notes: All CVE users should reference CVE-2019-15679 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2017-4878 | Unknown | 2018-03-16 | Withdrawn CVE | Proof of concept only | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none |