Overview 10,092 matches · 8 in Waratek scope · 1 protected · 134 exploited · 109 CISA KEV · 229 public PoC · 71 EPSS ≥ 0.5
10,092matches
8in Waratek scope0.1%
1protected0.0%
134exploited1.3%
109CISA KEV1.1%
229public PoC2.3%
71EPSS ≥ 0.50.7%
Protected by Waratek
1
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
7
0.1%
Outside Waratek scope
56
0.6%
Not applicable
10,028
99.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
0.0%
partly blocked
0
0.0%
not blocked
10,091
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 3,670 / year
20062
Not applicable2
High2
not blocked2
Exploited1
No public exploit1
20071
Not applicable1
High1
not blocked1
No public exploit1
20083
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
20098
Not applicable8
Critical1
High6
Medium1
not blocked8
Exploited1
Working exploit published1
No public exploit6
201029
Not applicable29
Critical3
High23
Medium3
not blocked29
Exploited3
Working exploit published4
No public exploit22
201156
Not applicable56
High28
Medium28
not blocked56
No public exploit56
201281
Not applicable81
Critical1
High48
Medium32
not blocked81
Exploited2
Working exploit published1
No public exploit78
201342
Not applicable42
Critical4
High36
Medium2
not blocked42
Exploited4
Working exploit published4
No public exploit34
201430
Not applicable30
Critical3
High19
Medium6
Low2
not blocked30
Exploited4
Working exploit published2
No public exploit24
201545
Not applicable45
Critical4
High29
Medium12
not blocked45
Exploited5
Working exploit published5
No public exploit35
2016157
Not applicable157
Critical42
High103
Medium12
not blocked157
Exploited3
Working exploit published18
Forecast only1
No public exploit135
2017295
Outside Waratek scope1
Not applicable294
Critical48
High196
Medium51
not blocked295
Exploited3
Working exploit published18
Proof of concept only2
No public exploit272
2018432
Outside Waratek scope1
Not applicable431
Critical114
High279
Medium38
Low1
not blocked432
Exploited2
Working exploit published16
Proof of concept only3
Forecast only1
No public exploit410
2019574
Outside Waratek scope18
Not applicable556
Critical122
High351
Medium99
Low2
not blocked574
Exploited10
Working exploit published20
Proof of concept only2
Forecast only2
No public exploit540
2020380
Outside Waratek scope11
Not applicable369
Critical59
High241
Medium76
Low4
not blocked380
Exploited6
Working exploit published2
Proof of concept only4
Forecast only1
No public exploit367
2021557
No exploit published2
Outside Waratek scope9
Not applicable546
Critical57
High408
Medium84
Low8
not blocked557
Exploited24
Proof of concept only4
Forecast only13
No public exploit516
2022732
No exploit published1
Outside Waratek scope5
Not applicable726
Critical44
High536
Medium146
Low6
not blocked732
Exploited10
Working exploit published1
Proof of concept only53
No public exploit668
2023645
Outside Waratek scope2
Not applicable643
Critical34
High473
Medium136
Low2
not blocked645
Exploited14
Working exploit published2
Proof of concept only78
Forecast only3
No public exploit548
20241,264
No exploit published1
Outside Waratek scope2
Not applicable1,261
Critical113
High1,025
Medium111
Low15
not blocked1,264
Exploited18
Proof of concept only58
Forecast only1
No public exploit1,187
20251,089
Outside Waratek scope3
Not applicable1,086
Critical55
High916
Medium94
Low24
not blocked1,089
Exploited18
Working exploit published5
Proof of concept only43
No public exploit1,023
20263,670
Protected by Waratek1
No exploit published3
Outside Waratek scope4
Not applicable3,662
Critical424
High2,762
Medium418
Low64
Unknown2
blocked by ARMR today1
not blocked3,669
Exploited6
Working exploit published1
Proof of concept only145
No public exploit3,518
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-52790 | High | 2026-11-13 | Not applicable | Proof of concept only | BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, there is a library-level memory safety issue that is reachable from an unmodified official sample server (apps/server-basic/main.c) over BACnet/IP resulting in a stack-use-after-return in writable Device string properties. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0. |
| CVE-2026-15465 | Unknown | 2026-11-13 | Not applicable | No public exploit | Software installed and run as a non-privileged user may conduct improper GPU system calls through the DDK kernel module interface. Under unsupported use of the interface, a use-after-free condition may occur that can lead to kernel memory corruption, platform instability, or system reboot. The weakness occurs when software references memory after it has been released. Accessing memory after free may result in corruption of valid data structures, unexpected program behaviour, process crashes, or execution of unintended operations. |
| CVE-2026-128240 | Medium | 2026-11-13 | Not applicable | No public exploit | GPAC through 26.07.0 contains a use-after-free vulnerability in gf_sg_proto_del() in src/scenegraph/vrml_proto.c because gf_sg_reset() frees unregistered prototypes still referenced by scene commands. Attackers can supply a crafted XMT/BT scene declaring prototypes via commands, processed by MP4Box -chap, to trigger freed memory access and crash the process. |
| CVE-2026-128016 | High | 2026-11-13 | Not applicable | No public exploit | FrankenPHP before 1.13.4 contains a use-after-free vulnerability in worker mode that frees internal streams of SplTempFileObject or SplFileObject on php://temp instances surviving across requests. Remote clients can send requests reaching code that uses such persisted objects, causing reads of freed memory that leak garbage data or crash the process. |
| CVE-2026-128015 | High | 2026-11-13 | Not applicable | No public exploit | FrankenPHP before 1.13.4 contains a use-after-free vulnerability that leaves a dangling pointer to a freed environment table when putenv() is called during request shutdown. Attackers triggering putenv() in shutdown functions, destructors, or session handlers can crash the process on the next getenv() call or leak previous request environment values. |
| CVE-2026-120221 | High | 2026-11-13 | Not applicable | No public exploit | In FRRouting 8.4 and later, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected. |
| CVE-2026-121753 | High | 2026-11-12 | Not applicable | No public exploit | Ashlar-Vellum Cobalt XE File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ashlar-Vellum Cobalt. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of XE files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28587. |
| CVE-2026-121742 | High | 2026-11-12 | Not applicable | No public exploit | Ashlar-Vellum Cobalt XE File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Ashlar-Vellum Cobalt. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of XE files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-28757. |
| CVE-2026-121741 | High | 2026-11-12 | Not applicable | No public exploit | Trimble SketchUp SKP File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Trimble SketchUp. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SKP files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-30421. |
| CVE-2026-120152 | Medium | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL pg_show_all_settings() allows a database user to retrieve memory contents, via loading a module while the function is scanning custom-variable placeholders that the module replaces and frees. Within major versions 16-18, minor versions before PostgreSQL 18.7, 17.12, and 16.16 are affected. Versions before PostgreSQL 16 are unaffected. |
| CVE-2026-120150 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL expanded-record domain checks allows an object creator to execute arbitrary code as the operating system user running the database, via repeated checks of a domain over a composite type that cause reuse of a dangling memory-context pointer. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-120147 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in the PostgreSQL dblink extension allows an object creator to execute arbitrary code as the operating system user running the database, via type conversion code that re-enters dblink and closes a connection whose results an outer dblink call is reading. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-120143 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL trigger functions allows an object creator to execute arbitrary code as the operating system user running the database, via a cursor over a transition table. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116332 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL portal setup allows an object creator to execute arbitrary code as the operating system user running the database, via running user-defined code during planning or executor startup that closes the portal currently being prepared. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116323 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL pltcl allows an object creator to execute arbitrary code as the operating system user running the database, via a domain CHECK that re-enters the Tcl interpreter and frees or changes a string still used by the outer result conversion. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116320 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via dropping the final reference to a Perl array or hash while PostgreSQL is converting that object. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116319 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via reentrant return_next() calls. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116310 | Medium | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL COPY FROM error reporting allows a database user to disclose portions of server memory, via a longer input row following an ignored or nullified conversion error. file_fdw reaches the same code path in affected version 18. Within major versions 17-18, minor versions before PostgreSQL 18.7 and 17.12 are affected. Versions before PostgreSQL 17 are unaffected. |
| CVE-2026-116307 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via re-entering plperl and freeing a prepared query while an outer invocation is executing it. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-116304 | High | 2026-11-12 | Not applicable | No public exploit | Use after free in PostgreSQL coordination of anonymous RECORD type identifiers among parallel workers allows a database user to execute arbitrary code as the operating system user running the database, via causing one process to free a shared tuple descriptor while another process retains and later uses its address. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. |
| CVE-2026-126921 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126919 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in BrowserTag in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126918 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Layout in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126911 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-126909 | Critical | 2026-11-11 | Not applicable | No public exploit | Use after free in Passwords in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126904 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Compositing in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126901 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in PDF in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126900 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in CSS in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126899 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Elements in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126895 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in CSS in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-126892 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in MediaStream in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126891 | Medium | 2026-11-11 | Not applicable | No public exploit | Use after free in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126887 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Animation in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126886 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Frames in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126885 | Critical | 2026-11-11 | Not applicable | No public exploit | Use after free in ServiceWorker in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-126883 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Core in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126879 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Layout in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-126877 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Dawn in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126873 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Extensions in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126869 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Frames in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126867 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Browser in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126865 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in DOM in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126864 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126863 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in HTML in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126861 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Media in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126852 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in MediaStream in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126851 | High | 2026-11-11 | Not applicable | No public exploit | Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-126846 | Critical | 2026-11-11 | Not applicable | No public exploit | Use after free in Skia in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-126842 | Critical | 2026-11-11 | Not applicable | No public exploit | Use after free in ANGLE in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-124740 | Medium | 2026-11-11 | Not applicable | No public exploit | A flaw was found in BusyBox's udhcpc6 DHCPv6 client. A malicious server on the local network can trigger a use-after-free condition by responding with a crafted Dynamic Host Configuration Protocol for IPv6 (DHCPv6) reply packet lacking usable address options. This issue causes the client to read stale heap memory, which can result in a Denial of Service (DoS) due to an application crash or disclose previously assigned network address data in subsequent discovery requests. |
| CVE-2026-123874 | High | 2026-11-11 | Not applicable | No public exploit | A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0). |
| CVE-2026-123866 | High | 2026-11-11 | Not applicable | No public exploit | A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x. |
| CVE-2026-123864 | High | 2026-11-11 | Not applicable | No public exploit | A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x. |
| CVE-2026-119055 | Medium | 2026-11-11 | Not applicable | No public exploit | CWE- 416: Use After Free vulnerability exists that could cause arbitrary code execution when a local attacker could trick the end user to open a specially crafted malicious SSD file. |
| CVE-2026-96994 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Winsock allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96992 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows PCI Bus Driver allows an unauthorized attacker to elevate privileges with a physical attack. |
| CVE-2026-96983 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows DNS allows an unauthorized attacker to deny service over an adjacent network. |
| CVE-2026-96978 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Credential User Interface allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96973 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Encrypting File System (EFS) allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96971 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows NetBIOS allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96179 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in DNS Server allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96177 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in DNS Server allows an unauthorized attacker to execute code over a network. |
| CVE-2026-96171 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96155 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Audio Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96124 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96110 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows OLE allows an authorized attacker to disclose information locally. |
| CVE-2026-96092 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in DNS Server allows an unauthorized attacker to execute code over a network. |
| CVE-2026-96076 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows DIAL Client allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96073 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96072 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Connected User Experiences and Telemetry allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96061 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96059 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in HID class driver allows an authorized attacker to disclose information locally. |
| CVE-2026-96047 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96046 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96043 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Connection Manager Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96042 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Connection Manager Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96035 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96027 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96026 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96023 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Push Notification Core allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96017 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in DNS Server allows an authorized attacker to deny service over a network. |
| CVE-2026-96008 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96007 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Connected Devices Platform Service (Cdpsvc) allows an authorized attacker to elevate privileges locally. |
| CVE-2026-96004 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Installer allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95997 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Event Logging Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95991 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95989 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in vhdmp.sys allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95987 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows User Manager Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95979 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Brokering File System allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95976 | High | 2026-11-10 | Not applicable | No public exploit | Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Diagnostic Policy Service allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95968 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Smart Card allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95966 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95962 | Critical | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Virtual Filtering Platform (VFP) allows an unauthorized attacker to execute code over a network. |
| CVE-2026-95956 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows eSCL Scanner allows an unauthorized attacker to execute code over a network. |
| CVE-2026-95913 | Medium | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Hyper-V allows an unauthorized attacker to deny service over a network. |
| CVE-2026-95895 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95885 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Client for NFS allows an unauthorized attacker to elevate privileges over a network. |
| CVE-2026-95876 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Windows Local Session Manager (LSM) allows an authorized attacker to elevate privileges locally. |
| CVE-2026-95691 | Unknown | 2026-11-10 | Not applicable | No public exploit | Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary. |
| CVE-2026-94522 | High | 2026-11-10 | Not applicable | No public exploit | Use after free in Kernel Transaction Manager allows an authorized attacker to elevate privileges locally. |