WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Published to 2026-07-31✕
Overview 18,860 matches · 1 in Waratek scope · 1 protected · 7 exploited · 0 CISA KEV · 132 public PoC · 0 EPSS ≥ 0.5
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,024 5.4% Withdrawn CVE 17,835 94.6%
Critical 0 0.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 18,860 100.0%
blocked by ARMR today 1 0.0% partly blocked 0 0.0% not blocked 18,859 100.0% not established 0 0.0% unrecorded 0 0.0%
split by peak 3,471 / year
Withdrawn CVE: 17,835Not applicable: 1,024Protected by Waratek: 1 Unknown: 18,860 not blocked: 18,859blocked by ARMR today: 1 No public exploit: 18,723Proof of concept only: 12Working exploit published: 118Exploited: 7
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,552 Not applicable117 Withdrawn CVE1,435 Unknown1,552 not blocked1,552 Exploited1 Proof of concept only1 No public exploit1,550
199319961999200220052008201120142017202020232026
18,860 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 1 of 189 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2026-9611 Unknown 2026-07-31 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-6890 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-6889 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-68577 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: Reserved via standalone CLI outside the OSIM flaw workflow; releasing so the CVE ID can be properly reserved and linked through OSIM when the flaw is worked.
CVE-2026-68576 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: Reserved via standalone CLI outside the OSIM flaw workflow; releasing so the CVE ID can be properly reserved and linked through OSIM when the flaw is worked.
CVE-2026-68575 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: Reserved via standalone CLI outside the OSIM flaw workflow; releasing so the CVE ID can be properly reserved and linked through OSIM when the flaw is worked.
CVE-2026-68574 Unknown 2026-07-31 Withdrawn CVE No public exploit Rejected reason: Reserved via standalone CLI outside the OSIM flaw workflow; releasing so the CVE ID can be properly reserved and linked through OSIM when the flaw is worked.
CVE-2026-51301 Unknown 2026-07-31 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-51299 Unknown 2026-07-31 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-51289 Unknown 2026-07-31 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-51288 Unknown 2026-07-31 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-51287 Unknown 2026-07-31 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-51286 Unknown 2026-07-31 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-51285 Unknown 2026-07-31 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-51284 Unknown 2026-07-31 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-51283 Unknown 2026-07-31 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-51282 Unknown 2026-07-31 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-51281 Unknown 2026-07-31 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-51280 Unknown 2026-07-31 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-51279 Unknown 2026-07-31 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-51278 Unknown 2026-07-31 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-51277 Unknown 2026-07-31 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-51276 Unknown 2026-07-31 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-51265 Unknown 2026-07-31 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-51264 Unknown 2026-07-31 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-51262 Unknown 2026-07-31 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-51258 Unknown 2026-07-31 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-51257 Unknown 2026-07-31 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-51256 Unknown 2026-07-31 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-51255 Unknown 2026-07-31 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-51253 Unknown 2026-07-31 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-51250 Unknown 2026-07-31 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-51249 Unknown 2026-07-31 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-51248 Unknown 2026-07-31 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-51247 Unknown 2026-07-31 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-51246 Unknown 2026-07-31 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-51245 Unknown 2026-07-31 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-51243 Unknown 2026-07-31 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-51242 Unknown 2026-07-31 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-51241 Unknown 2026-07-31 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-51240 Unknown 2026-07-31 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-51239 Unknown 2026-07-31 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-51238 Unknown 2026-07-31 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-51237 Unknown 2026-07-31 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-51236 Unknown 2026-07-31 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-51234 Unknown 2026-07-31 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-51233 Unknown 2026-07-31 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-51232 Unknown 2026-07-31 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-51231 Unknown 2026-07-31 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-51230 Unknown 2026-07-31 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-51229 Unknown 2026-07-31 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-17592 Unknown 2026-07-31 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-51295 Unknown 2026-07-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-51294 Unknown 2026-07-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-51293 Unknown 2026-07-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-51292 Unknown 2026-07-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-51291 Unknown 2026-07-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-51290 Unknown 2026-07-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-51272 Unknown 2026-07-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-67188 Unknown 2026-07-29 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-66737 Unknown 2026-07-29 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-66051 Unknown 2026-07-29 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-51992 Unknown 2026-07-29 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. ClickHouse's PostgreSQL integration intentionally allows users with valid PostgreSQL credentials to execute queries against a remote PostgreSQL server. No vulnerability in ClickHouse is exploited; code execution occurs on the downstream PostgreSQL server using credentials explicitly provided by the user with specific pg_execute_server_program permission, exploiting a feature that was wrongly reported as CVE-2019-9193 in PostgreSQL (https://www.postgresql.org/about/news/cve-2019-9193-not-a-security-vulnerability-1935/).
CVE-2026-18060 Unknown 2026-07-29 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-16339 Unknown 2026-07-29 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-51275 Unknown 2026-07-28 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-51274 Unknown 2026-07-28 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-51273 Unknown 2026-07-28 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-51271 Unknown 2026-07-28 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-51270 Unknown 2026-07-28 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-51269 Unknown 2026-07-28 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-51268 Unknown 2026-07-28 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-51267 Unknown 2026-07-28 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-51266 Unknown 2026-07-28 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-51263 Unknown 2026-07-28 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-51261 Unknown 2026-07-28 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-51260 Unknown 2026-07-28 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-51259 Unknown 2026-07-28 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-51254 Unknown 2026-07-28 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-51252 Unknown 2026-07-28 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-51251 Unknown 2026-07-28 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-14170 Unknown 2026-07-28 Withdrawn CVE No public exploit Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-51304 Unknown 2026-07-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-51303 Unknown 2026-07-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-51302 Unknown 2026-07-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-51300 Unknown 2026-07-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-51298 Unknown 2026-07-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-51297 Unknown 2026-07-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-51296 Unknown 2026-07-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-51244 Unknown 2026-07-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-51235 Unknown 2026-07-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-15799 Unknown 2026-07-27 Withdrawn CVE No public exploit Rejected reason: This is a duplicate.
CVE-2026-64514 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: userfaultfd: gate must_wait writability check on pte_present() userfaultfd_must_wait() and userfaultfd_huge_must_wait() read the PTE without taking the page table lock and then apply pte_write() / huge_pte_write() to it. Those accessors decode bits from the present encoding only; on a swap or migration entry they read the offset bits that happen to share the same position and return an undefined result. The intent of the check is "is this fault still WP-blocked?". A non-marker swap entry means the page is in transit -- the userfault context the original fault delivered against is no longer the same, and the swap-in or migration completion path will re-deliver a fresh fault if userspace still needs to handle it. Worst case under the current code the garbage write bit says "wait", and the thread stays asleep until a UFFDIO_WAKE that may never arrive. Gate the writability check on pte_present() so the lockless re-check only inspects present-PTE bits when the entry is actually present. The non-present, non-marker case returns "don't wait" and lets the fault path retry.
CVE-2026-64513 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally recompute CR8 intercept on PPR update The TPR_THRESHOLD field in the VMCS is used by VMX to induce VM exits when the guest's virtual TPR falls under the specified threshold, allowing KVM to inject previously masked interrupts. KVM handles these VM exits in handle_tpr_below_threshold(). Commit eb90f3417a0c ("KVM: vmx: speed up TPR below threshold vmexits") optimized this function by calling apic_update_ppr() instead of raising KVM_REQ_EVENT. apic_update_ppr() then raises KVM_REQ_EVENT if there is a pending, deliverable interrupt. However, if there are no new interrupts pending, apic_update_ppr() does not issue the request. Thus, kvm_lapic_update_cr8_intercept() and vmx_update_cr8_intercept() are not called before VM entry, which results in a high, stale TPR_THRESHOLD. This is problematic due to the following sentence in 28.2.1.1 "VM-Execution Control Fields" in the SDM: The following check is performed if the “use TPR shadow” VM-execution control is 1 and the “virtualize APIC accesses” and “virtual-interrupt delivery” VM-execution controls are both 0: the value of bits 3:0 of the TPR threshold VM-execution control field should not be greater than the value of bits 7:4 of VTPR. This error condition is typically not observed when KVM runs on a bare metal system because modern processors support APICv, which enables virtual-interrupt delivery, and which KVM uses when possible. This causes the processor to no longer generate TPR-below-threshold exits and to no longer check TPR_THRESHOLD on entry. However, when running on older platforms, or under nested virtualization on a hypervisor that does not support virtual-interrupt delivery and enforces this check (like Hyper-V) this can cause a VM entry failure with hardware error 0x7, as seen in [1]. Call kvm_lapic_update_cr8_intercept() if apic_update_ppr() does not find a deliverable interrupt (and thus does not raise KVM_REQ_EVENT). Remove calls to kvm_lapic_update_cr8_intercept() on paths that end up in apic_update_ppr(), as they now become redundant. This ensures that any path that updates the guest's PPR also figures out if KVM needs to wait for a TPR change (using TPR_THRESHOLD on VMX or CR8 intercepts on SVM).
CVE-2026-64512 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Suppress UBSAN warning caused by field misuse The definition of reg->access_width changes depending on the reg->space_id type. Type ACPI_ADR_SPACE_PLATFORM_COMM uses access_width to indicate the PCC region, which can result in a UBSAN if the value is greater than 4. For example: UBSAN: shift-out-of-bounds in drivers/acpi/cppc_acpi.c:1090:9 shift exponent 32 is too large for 32-bit type 'int' CPU: 61 UID: 0 PID: 1220 Comm: (udev-worker) Not tainted 7.0.10-201.fc44.aarch64 #1 PREEMPT(lazy) Hardware name: To be filled by O.E.M. Call trace: ...(trimming) ubsan_epilogue+0x10/0x48 __ubsan_handle_shift_out_of_bounds+0xdc/0x1e0 cpc_write+0x4d0/0x670 cppc_set_perf+0x18c/0x490 cppc_cpufreq_cpu_init+0x1c8/0x380 [cppc_cpufreq] ... (trimming) Lets fix this by validating the region type, as well as whether access_width has a value. Then since we are returning bit_width directly for ACPI_ADR_SPACE_PLATFORM_COMM, drop the code correcting the size.
CVE-2026-64503 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error kxsd9_write_raw() takes a runtime PM reference with pm_runtime_get_sync() but returns -EINVAL directly when a scale with a non-zero integer part is requested, skipping the matching pm_runtime_put_autosuspend(). This leaks a runtime PM usage-counter reference on every such write, after which the device can no longer autosuspend. Set the error code and fall through to the existing put instead of returning early.
CVE-2026-64500 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: iio: adc: lpc32xx: Initialize completion before requesting IRQ In the report from Jaeyoung Chung: "lpc32xx_adc_probe() in drivers/iio/adc/lpc32xx_adc.c registers its interrupt handler with devm_request_irq() before it initializes st->completion with init_completion(). If an interrupt arrives after devm_request_irq() and before init_completion(), the handler calls complete() on an uninitialized completion, causing a kernel panic. The probe path, in lpc32xx_adc_probe(): iodev = devm_iio_device_alloc(&pdev->dev, sizeof(*st)); /* st kzalloc-zeroed */ ... retval = devm_request_irq(&pdev->dev, irq, lpc32xx_adc_isr, 0, LPC32XXAD_NAME, st); /* register handler */ ... init_completion(&st->completion); /* initialize completion */ lpc32xx_adc_isr() calls complete(): complete(&st->completion); If the device raises an interrupt before init_completion() runs, complete() acquires the uninitialized wait.lock and walks the zeroed task_list in swake_up_locked(). The zeroed task_list makes list_empty() return false, so swake_up_locked() dereferences a NULL list entry, triggering a KASAN wild-memory-access." Fix the chance of a spurious IRQ causing an uninitialized pointer dereference by moving init_completion() above devm_request_irq().
CVE-2026-64499 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: iio: adc: ti-ads1119: fix PM reference leak in buffer preenable ads1119_triggered_buffer_preenable() resumes the device with pm_runtime_resume_and_get() before starting a conversion. If i2c_smbus_write_byte() fails, the function returns the error directly and leaves the runtime PM usage counter elevated. The matching postdisable callback is not called when preenable fails, so the reference is leaked and the device may remain runtime-active indefinitely. Store the I2C transfer result in ret and drop the runtime PM reference on failure before returning the error.
CVE-2026-64498 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: iio: buffer: hw-consumer: free scan_mask on buffer release The scan_mask lifetime changed in commit 9a2e1233d38c ("iio: buffer: hw-consumer: remove redundant scan_mask flexible array"). Before that change, the scan mask storage was embedded in struct hw_consumer_buffer, so iio_hw_buf_release() could free the whole allocation with a single kfree(hw_buf). That commit moved the scan mask to a separate bitmap_zalloc() allocation stored in buffer.scan_mask, but left iio_hw_buf_release() unchanged. Free the scan mask in iio_hw_buf_release() before freeing the buffer wrapper.
CVE-2026-64497 Unknown 2026-07-25 Not applicable No public exploit In the Linux kernel, the following vulnerability has been resolved: iio: chemical: scd30: Cleanup initializations and fix sign-extension bug Include linux/bitfield.h for FIELD_GET(). Create new macros for bit manipulation in combination with manual bit manipulation being replaced with FIELD_GET(). The current variable declaration and initializations are barely readable and use comma separations across multiple lines. Refactor the initializations so that mantissa and exp have separate declarations and sign gets initialized later. In addition (and due to the nature of the cleanup), fix a sign-extension bug where, float32 would get bitwise anded with ~BIT(31) (which is 0xFFFFFFFF7FFFFFFF) which corrupted the exponent.
‹ prev page 1 of 189 next ›