Overview 224,361 matches · 9,000 in Waratek scope · 687 protected · 3,017 exploited · 748 CISA KEV · 4,236 public PoC · 1,026 EPSS ≥ 0.5
224,361matches
9,000in Waratek scope4.0%
687protected0.3%
3,017exploited1.3%
748CISA KEV0.3%
4,236public PoC1.9%
1,026EPSS ≥ 0.50.5%
Protected by Waratek
692
0.3%
Rule in development
4
0.0%
Mitigation candidate
124
0.1%
No exploit published
8,180
3.6%
Outside Waratek scope
710
0.3%
Not applicable
207,160
92.3%
Withdrawn CVE
7,491
3.3%
Critical
25,608
11.4%
High
85,348
38.0%
Medium
91,023
40.6%
Low
10,745
4.8%
None
79
0.0%
Unknown
11,558
5.2%
split by
peak 37,712 / quarter
Q1 237,822
Protected by Waratek41
Mitigation candidate2
No exploit published165
Outside Waratek scope58
Not applicable6,709
Withdrawn CVE847
Critical1,323
High2,795
Medium2,797
Low60
Unknown847
blocked by ARMR today41
not blocked7,781
Exploited141
Working exploit published134
Proof of concept only1,603
Forecast only39
No public exploit5,905
Q2 237,502
Protected by Waratek42
Mitigation candidate16
No exploit published296
Outside Waratek scope46
Not applicable6,732
Withdrawn CVE370
Critical1,129
High2,804
Medium3,111
Low88
Unknown370
blocked by ARMR today42
not blocked7,459
not established1
Exploited144
Working exploit published192
Proof of concept only1,451
Forecast only28
No public exploit5,687
Q3 237,709
Protected by Waratek39
Mitigation candidate8
No exploit published187
Outside Waratek scope48
Not applicable6,648
Withdrawn CVE779
Critical1,211
High2,780
Medium2,833
Low106
Unknown779
blocked by ARMR today39
not blocked7,670
Exploited148
Working exploit published149
Proof of concept only1,607
Forecast only15
No public exploit5,790
Q4 237,916
Protected by Waratek39
Mitigation candidate14
No exploit published234
Outside Waratek scope53
Not applicable7,439
Withdrawn CVE137
Critical1,368
High3,258
Medium3,083
Low69
Unknown138
blocked by ARMR today39
not blocked7,876
not established1
Exploited134
Working exploit published82
Proof of concept only931
Forecast only28
No public exploit6,741
Q1 248,905
Protected by Waratek35
Mitigation candidate13
No exploit published202
Outside Waratek scope49
Not applicable8,382
Withdrawn CVE224
Critical1,418
High3,330
Medium3,792
Low138
Unknown227
blocked by ARMR today35
not blocked8,870
Exploited181
Working exploit published100
Proof of concept only1,924
Forecast only15
No public exploit6,685
Q2 2412,011
Protected by Waratek21
Mitigation candidate4
No exploit published165
Outside Waratek scope41
Not applicable11,467
Withdrawn CVE313
Critical1,220
High4,552
Medium5,688
Low236
Unknown315
blocked by ARMR today21
not blocked11,990
Exploited212
Working exploit published100
Proof of concept only1,809
Forecast only53
No public exploit9,837
Q3 248,659
Protected by Waratek25
Mitigation candidate6
No exploit published111
Outside Waratek scope24
Not applicable8,357
Withdrawn CVE136
Critical1,045
High3,302
Medium4,016
Low160
Unknown136
blocked by ARMR today23
partly blocked2
not blocked8,634
Exploited168
Working exploit published109
Proof of concept only1,865
Forecast only8
No public exploit6,509
Q4 2411,129
Protected by Waratek27
Mitigation candidate5
No exploit published143
Outside Waratek scope72
Not applicable10,804
Withdrawn CVE78
Critical1,191
High4,148
Medium5,502
Low206
None1
Unknown81
blocked by ARMR today27
not blocked11,102
Exploited186
Working exploit published94
Proof of concept only1,869
Forecast only7
No public exploit8,973
Q1 2512,412
Protected by Waratek21
Mitigation candidate4
No exploit published151
Outside Waratek scope23
Not applicable11,747
Withdrawn CVE466
Critical1,155
High4,302
Medium6,190
Low299
Unknown466
blocked by ARMR today21
not blocked12,391
Exploited168
Working exploit published138
Proof of concept only2,411
Forecast only7
No public exploit9,688
Q2 2512,205
Protected by Waratek32
Rule in development1
Mitigation candidate8
No exploit published153
Outside Waratek scope31
Not applicable11,470
Withdrawn CVE510
Critical1,093
High3,931
Medium6,106
Low559
None6
Unknown510
blocked by ARMR today32
not blocked12,173
Exploited196
Working exploit published89
Proof of concept only2,808
Forecast only9
No public exploit9,103
Q3 2512,207
Protected by Waratek23
Rule in development1
Mitigation candidate6
No exploit published238
Outside Waratek scope39
Not applicable11,418
Withdrawn CVE482
Critical1,205
High3,992
Medium5,277
Low1,250
None1
Unknown482
blocked by ARMR today23
not blocked12,184
Exploited190
Working exploit published295
Proof of concept only3,018
Forecast only1
No public exploit8,703
Q4 2513,148
Protected by Waratek27
Rule in development2
Mitigation candidate7
No exploit published189
Outside Waratek scope46
Not applicable12,513
Withdrawn CVE364
Critical1,037
High4,445
Medium5,470
Low932
None3
Unknown1,261
blocked by ARMR today27
not blocked13,119
not established2
Exploited173
Working exploit published72
Proof of concept only2,754
No public exploit10,149
Q1 2616,255
Protected by Waratek33
Mitigation candidate9
No exploit published160
Outside Waratek scope62
Not applicable14,888
Withdrawn CVE1,103
Critical1,663
High5,966
Medium6,183
Low1,211
None33
Unknown1,199
blocked by ARMR today33
not blocked16,221
not established1
Exploited197
Working exploit published134
Proof of concept only4,214
Forecast only3
No public exploit11,707
Q2 2620,871
Protected by Waratek94
Mitigation candidate10
No exploit published754
Outside Waratek scope49
Not applicable19,781
Withdrawn CVE183
Critical2,294
High8,530
Medium8,222
Low1,631
None11
Unknown183
blocked by ARMR today94
not blocked20,777
Exploited249
Working exploit published148
Proof of concept only5,197
Forecast only2
No public exploit15,275
Q3 2637,712
Protected by Waratek123
Mitigation candidate11
No exploit published3,204
Outside Waratek scope47
Not applicable33,566
Withdrawn CVE761
Critical4,751
High15,836
Medium12,161
Low2,204
None19
Unknown2,741
blocked by ARMR today121
partly blocked2
not blocked37,589
Exploited308
Working exploit published146
Proof of concept only6,502
No public exploit30,756
Q4 2627,898
Protected by Waratek70
Mitigation candidate1
No exploit published1,828
Outside Waratek scope22
Not applicable25,239
Withdrawn CVE738
Critical2,505
High11,377
Medium10,592
Low1,596
None5
Unknown1,823
blocked by ARMR today69
partly blocked1
not blocked27,828
Exploited222
Working exploit published46
Proof of concept only3,737
No public exploit23,893
Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-99319 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Refuse a retried DSP load after a failure snd_usx2y_hwdep_dsp_load() sets up the asynchronous sequence URBs and the interrupt URB when the FPGA firmware image with index 1 is loaded, and then creates the ALSA devices. If usx2y_in04_init() or usx2y_create_alsa_devices() fails, the URBs that were already set up are left in place. The core keeps the index unloaded when the callback fails, so user space may issue the same request again. The second attempt then enters usx2y_async_seq04_init() or usx2y_in04_init() with the URBs still allocated and trips WARN_ON(usx2y->as04.buffer) or WARN_ON(usx2y->in04_urb). The URBs cannot be released at this point: the card may already have registered PCM devices that user space can still open, and the disconnect handler accesses the URBs without holding the DSP lock. Mark the chip as hung instead, so that a retried request is refused with -ENODEV and the assertions keep their meaning. The URBs are released by snd_usx2y_card_private_free() when the card is freed. A failing usx2y_async_seq04_init() still releases its own URBs, so that path remains retryable. |
| CVE-2026-99318 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close bcd2000_disconnect() calls snd_card_disconnect(), which only prevents new opens, and then frees the MIDI URBs. A rawmidi file that was already open can still be closed afterwards, and its close callback, bcd2000_midi_output_close(), calls usb_kill_urb() on midi_out_urb. The URB pointers are cleared on disconnect and their accesses are serialized with midi_lock, but bcd2000_midi_output_close() reads midi_out_urb without that lock. The check can therefore pass just before the pointer is cleared, and usb_kill_urb() then runs on the URB that has already been freed: BUG: KASAN: slab-use-after-free in usb_kill_urb+0x74/0x80 Read of size 8 at addr ffff8880078e7d40 usb_kill_urb bcd2000_midi_output_close close_substream rawmidi_release_priv snd_rawmidi_release Allocated by: usb_alloc_urb <- bcd2000_init_midi <- bcd2000_probe Freed by: usb_free_urb <- bcd2000_midi_free <- bcd2000_disconnect Take the lock in bcd2000_midi_output_close() and reference the URB with usb_get_urb() before releasing it. The URB then stays valid until usb_put_urb() after usb_kill_urb() has returned, even if a disconnect frees it in the meantime. usb_kill_urb() itself cannot run under midi_lock, as the completion handler takes the same lock. |
| CVE-2026-99317 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: hwdep: Serialize DSP load requests The check of the loaded DSP indices and the call of the driver's dsp_load callback in snd_hwdep_dsp_load() are not serialized. A hwdep file descriptor can be shared among threads, or inherited across fork, so two SNDRV_HWDEP_IOCTL_DSP_LOAD requests for the same index can both observe the index as unloaded and enter the driver's callback concurrently, even though the device itself is opened exclusively. This breaks the assumption behind hw->dsp_loaded that a firmware index is loaded only once. For example, snd-usb-usx2y hits WARN_ON(usx2y->as04.buffer) in usx2y_async_seq04_init() and may allocate the US-428 sequence URBs twice. Serialize the check, the callback invocation and the bookkeeping with a per-hwdep mutex, so that the second request returns -EBUSY. |
| CVE-2026-99316 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Initialize idle URBs before submitting streams usb_stream_start() submits the first two capture and playback URBs and only afterwards assigns sk->idle_inurb, sk->idle_outurb, sk->completed_inurb and sk->completed_outurb to the remaining two URBs of each direction. A transfer can complete as soon as usb_submit_urb() has been called, so the completion handler i_capture_start() or i_playback_start() may run before those pointers are set. While the stream is still being synchronized (state below usb_stream_sync1), stream_start() then calls playback_prep_freqn(sk, sk->idle_outurb) with sk->idle_outurb still NULL, and the packet descriptors are written through that NULL pointer: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000018: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in range [0x00000000000000c0-0x00000000000000c7] RIP: 0010:playback_prep_freqn+0x11c/0x4a0 sound/usb/usx2y/usb_stream.c:33 Call Trace: <IRQ> stream_start+0x5dc/0x8d0 sound/usb/usx2y/usb_stream.c:596 i_capture_start+0x3da/0x710 sound/usb/usx2y/usb_stream.c:654 __usb_hcd_giveback_urb+0x238/0x550 drivers/usb/core/hcd.c:1657 usb_giveback_urb_bh+0x20b/0x530 drivers/usb/core/hcd.c:1691 tasklet_hi_action+0xa/0x20 kernel/softirq.c:994 handle_softirqs+0x16f/0x440 kernel/softirq.c:645 </IRQ> The four URBs referenced by these pointers are allocated long before and do not depend on any transfer state, so assign them before the submit loop. Keeping the assignment inside the retry path also restores a well-defined URB rotation when the start frame mismatch handling kills and resubmits the streams. |
| CVE-2026-99315 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Fix NULL dereference at hwdep open and release usb_stream_hwdep_open() and usb_stream_hwdep_release() pass the result of usb_ifnum_to_if() straight to usb_autopm_get_interface() and usb_autopm_put_interface(), without checking it for NULL. usb_ifnum_to_if() returns NULL once the device is gone, since usb_disable_device() clears udev->actconfig on disconnect. The hwdep file can outlive the disconnect: the card is released with snd_card_free_when_closed(), so a process that keeps the character device open reaches the driver's release callback after the USB configuration has been dropped, and interface_to_usbdev() then dereferences the NULL interface at offsetof(struct device, parent). The open callback has the same problem when it races with the disconnect. Check both lookups and fail the open with -ENODEV; in release, skip the runtime PM put when the interface is already gone and still run the rest of the per-file cleanup. Move the us122l->first bookkeeping after the checks so that a failed open no longer leaves a stale file pointer behind. |
| CVE-2026-99314 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap() usb_stream_hwdep_mmap() reads us122l->sk.s and dereferences it without checking for NULL. The stream object is released by usb_stream_free(), which is reached through us122l_stop() both when the device is disconnected and when us122l_start() fails, and it leaves us122l->sk.s set to NULL. The hwdep file stays usable after that, so a later mmap() KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:usb_stream_hwdep_mmap+0x107/0x890 sound/usb/usx2y/us122l.c:182 crashes while reading s->read_size, which sits at offset 0x10. That NULL is an expected state for this field: usb_stream_hwdep_vm_fault(), usb_stream_hwdep_poll(), usb_stream_hwdep_ioctl(), usb_stream_stop() and usb_stream_free() all test it before use. Only the mmap callback misses the check, so let it return -ENODEV, matching what the other hwdep mapping in usx2yhwdeppcm.c does when its shared buffer has not been allocated. |
| CVE-2026-99313 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack pointer The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous command path (__do_hidpp_send_message_sync). However, this pointer is not cleared when the function returns. If an event is processed (e.g. by a different thread) while the send_mutex is held by a new command, but before that command has updated send_receive_buf, the handler (hidpp_raw_hidpp_event) will observe that the mutex is locked and dereference the stale pointer. This results in an out-of-bounds access on a different thread's kernel stack (or a NULL pointer dereference on the very first command). Fix this by: 1. Clearing hidpp->send_receive_buf to NULL before releasing the mutex in the synchronous command path. 2. Moving the assignment of the local 'question' and 'answer' pointers inside the mutex_is_locked() block in the handler, and adding a NULL check before dereferencing. |
| CVE-2026-99312 | Unknown | 2026-11-18 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally reset MMU context when emulating INIT Force an MMU reset when emulating an INIT even if paging was already disabled, as the MMU page role includes guest_mode (L2), i.e. an INIT while L2 is running with CR0.PG=0 will result in KVM running L1 with a stale MMU context. Alternatively, the reset could be scoped strictly to paging being enabled or L2 being active, but SMM is also encoded in the page role. Even though it _should_ be impossible for the vCPU to be INIT'd while SMM is active, there's zero value in not handling SMM. At that point, the only scenario where KVM _doesn't_ need to reset the MMU context is on an INIT with the vCPU running in Real Mode or Unpaged Protect Mode, and while INIT in those modes is somewhat common, it's far from a hot path and re-initializing the MMU is not expensive, especially when the role isn't changing (KVM elides most of the re-configuration in that case). Note, like the Fixes commit, this bug only affects nested SVM as INIT is an unconditional intercept on VMX, i.e. it's impossible to emulate INIT while L2 is active. Temporarily keep the guest TLB flush when CR0.PG is being cleared even though it is fully redundant with the flush that is emitted on all INIT events (KVM itself only does RESET when a vCPU is being created, i.e. when CR0.PG must be '0'). |
| CVE-2026-97330 | Unknown | 2026-11-18 | Not applicable | No public exploit | The Team Members WordPress plugin before 5.4.2 does not properly escape team member social link URLs when they are rendered back in the administration area, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks against higher privileged users who edit the team. |
| CVE-2026-97329 | Unknown | 2026-11-18 | Not applicable | No public exploit | The Team Members WordPress plugin before 5.4.2 does not properly escape a team member field when it is rendered back in the administration area, allowing users with the contributor role and above to perform Stored Cross-Site Scripting attacks against higher-privileged users who edit the team. |
| CVE-2026-96841 | Medium | 2026-11-18 | Not applicable | No public exploit | The ITRO Popup Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_html' parameter in all versions up to, and including, 5.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable by low-privileged roles such as Subscriber when an administrator has explicitly granted that role access to the plugin settings page via the plugin's role selection option. |
| CVE-2026-96665 | High | 2026-11-18 | Not applicable | No public exploit | The SendPress Newsletters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sp_firstname' parameter in all versions up to, and including, 1.26.1.20 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The public subscriber-management route uses an unsigned, forgeable base64-encoded JSON token, allowing an unauthenticated attacker to impersonate any subscriber and obtain a valid nonce — bypassing the POST handler's only access control check. |
| CVE-2026-96571 | High | 2026-11-18 | Not applicable | No public exploit | The FancyBox for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Anchor 'href' Attribute in all versions up to, and including, 3.4.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to wrap the payload anchor around a smilie shortcode (e.g., :mrgreen:), which WordPress renders as an <img> element, satisfying the plugin's a:has(img) enrollment selector and disguising the malicious link as an ordinary comment emoticon. |
| CVE-2026-95823 | High | 2026-11-18 | Not applicable | No public exploit | tcp_pkt_linearize() in subsys/net/ip/tcp.c is used by th_get() whenever a received TCP header is not contiguous in a single net_buf. While pulling the header bytes out of the following fragments, the loop called net_buf_unref() on an emptied fragment without first detaching its frags pointer. net_buf_unref() walks the whole fragment list, so the payload buffers still linked behind that fragment were freed as well, and the stale pointer was then reinstalled into the packet as buf->frags, producing a use-after-free and a later double free during packet teardown. The same loop also advanced to second->frags unconditionally: when the fragment still held payload after the header remainder was pulled, it was spliced out of the packet without ever being unreferenced, permanently leaking that buffer and silently dropping the data it carried. The defect is reached from tcp_recv() via th_get() on every received TCP segment, before connection lookup or any header validation, so a single unauthenticated segment that matches a listening socket is sufficient. An attacker only needs the TCP header to straddle a net_buf boundary, which they can arrange from off-link: IPv6 extension headers are accepted on receive and their length is added to the header offset by th_get(), so a Destination Options header of a suitable length places the TCP header across the boundary of the fixed-size receive buffers (CONFIG_NET_BUF_DATA_SIZE). Packet chains assembled from several sources - IPv4/IPv6 reassembly, 6LoWPAN/802.15.4 reassembly, tunnel or virtual interfaces that strip an outer header, or drivers producing scatter-gather chains - can additionally present a short interior fragment that the loop empties exactly, which is the case that frees the remainder of the packet while it is still in use. The reliably reachable consequence is exhaustion of the receive buffer pool: each crafted segment leaks one net_buf from the fixed CONFIG_NET_BUF_RX_COUNT pool, the buffers are never reclaimed, and once the pool is empty the device can no longer receive network traffic until it is rebooted. Where a fragment is emptied exactly, the impact rises to memory corruption: freed pool buffers are written through by the remainder of the loop, their contents may be delivered to the application, and the packet is double-freed on teardown. The fix saves and clears second->frags before the net_buf_unref() so only the emptied header fragment is released, and advances to the next fragment only when second->len == 0, keeping any fragment that still holds payload in the packet. This restores the detach-before-unref ownership pattern used elsewhere in the stack, for example in net_pkt_trim_buffer(). |
| CVE-2026-95791 | Medium | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the web management and file transfer component of AOS web could allow an authenticated remote attacker to perform arbitrary file reads. Successful exploitation could allow an attacker to access sensitive files on the underlying system, potentially exposing configuration data or credentials. |
| CVE-2026-95790 | Medium | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the web-based management interface of network device management systems of AOS-8 Mobility Controllers could allow an authenticated remote attacker to bypass authorization controls. Successful exploitation could allow a low-privilege attacker to read sensitive configuration data potentially leading to unauthorized network access and further compromise of network security. |
| CVE-2026-95789 | High | 2026-11-18 | Not applicable | No public exploit | Command injection vulnerability in the affected interface of AOS-10 or AOS-8 could allow an authenticated remote attacker to perform command injection only on certain impacted devices. Successful exploitation could allow an attacker to execute unauthorized arbitrary commands with the privileges of the affected mechanism on the underlying operating system. |
| CVE-2026-95788 | High | 2026-11-18 | Not applicable | No public exploit | An unauthenticated buffer overflow vulnerability exists in the underlying operating system of AOS-10 or AOS-8 and could allow an unauthenticated adjacent attacker to conduct a denial of service attack. Successful exploitation could allow an attacker to disrupt the availability of the affected system, with a limited impact to the integrity of the affected component. |
| CVE-2026-95787 | Critical | 2026-11-18 | Not applicable | No public exploit | Vulnerabilities in the PAPI protocol of AOS-10 could allow an unauthenticated remote attacker to circumvent existing authentication controls. Successful exploitation could allow an attacker to gain administrative access, modify system configurations, and access or manipulate sensitive data. |
| CVE-2026-95690 | Unknown | 2026-11-18 | Not applicable | No public exploit | Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory. |
| CVE-2026-95645 | Critical | 2026-11-18 | Not applicable | No public exploit | Zohocorp Manageengine DDI Central build below 6500 are affected by a authenticated command injection vulnerability in the Windows DDI Agent's clear_blocked_domains functionality, allowing specially crafted blocked-domain values to trigger arbitrary command execution on Windows systems. |
| CVE-2026-95643 | Critical | 2026-11-18 | Not applicable | No public exploit | Zohocorp Manageengine DDI Central build below 6500 are affected by a authenticated PowerShell command injection vulnerability in the Telnet connectivity feature, allowing specially crafted IPv6 scope identifiers to execute arbitrary commands on managed Windows nodes. |
| CVE-2026-93459 | High | 2026-11-18 | Not applicable | No public exploit | Use of externally-controlled format string in certain ASUS Router firmware allows a nearby administrator to read or write memory, potentially resulting in a denial-of-service, via crafted format specifiers sent to the logging/summary function. Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information. |
| CVE-2026-93458 | Medium | 2026-11-18 | Not applicable | No public exploit | Insertion of sensitive information into sent data in certain ASUS Router firmware allows a remote attacker to obtain router’s UID or login authorization tokens for the victim's linked account via a crafted web page, which requires a logged-in router administrator to actively complete the third-party authorization flow. Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information. |
| CVE-2026-92535 | Medium | 2026-11-18 | Not applicable | No public exploit | The Make Connector plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.6 via the include_custom_fields. This makes it possible for unauthenticated attackers to extract arbitrary admin-selected user, post, comment, and term metadata exposed via core REST endpoints — including active session tokens with source IP, user-agent, login and expiry timestamps, capability sets, and any other admin-selected private meta keys including protected underscore-prefixed entries. This is exploitable because the plugin's meta picker queries all meta keys from the database without filtering, offering protected underscore-prefixed keys such as session_tokens and wp_capabilities for administrator selection; if any such keys are selected, their values become readable without any credentials. |
| CVE-2026-92236 | Medium | 2026-11-18 | Not applicable | No public exploit | The Asset CleanUp: Page Speed Booster plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via 'wpacu_unload_css' and 'wpacu_unload_js' Query Parameters in all versions up to, and including, 1.4.0.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Successful exploitation requires that the victim has sufficient privileges to see the plugin's admin-bar entry, typically an administrator. |
| CVE-2026-92182 | High | 2026-11-18 | Not applicable | No public exploit | Netgate pfSense CE XMLRPC Incorrect Authorization Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Netgate pfSense. Authentication is required to exploit this vulnerability. The specific flaw exists within the XMLRPC endpoint. The issue results from incorrect authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code within the context of the root. Was ZDI-CAN-32353. |
| CVE-2026-89218 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to enforce the Access Control Policy's download_file_attachment check across several post- and file-serving code paths (bulk post retrieval, channel bookmarks, and persistent notification delivery), which allows an authenticated channel member denied a specific file's download to obtain that file's metadata and a rendered preview thumbnail via those endpoints and events.. Mattermost Advisory ID: MMSA-2026-00785 |
| CVE-2026-88902 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to bound the work performed while reading EXIF orientation metadata, which allows an authenticated user to cause disproportionate server-side CPU usage by uploading or linking a small image with specially structured EXIF metadata.. Mattermost Advisory ID: MMSA-2026-00784 |
| CVE-2026-88760 | Medium | 2026-11-18 | Not applicable | No public exploit | Missing Authentication for Critical Function in certain ASUS Router firmware allows unauthenticated nearby users to obtain router information and resources (e.g., multimedia files) via HTTP requests. Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information. |
| CVE-2026-88711 | High | 2026-11-18 | Not applicable | No public exploit | Improper neutralization of special elements used in an OS command in certain ASUS Router firmware models allows an remote attacker to to execute arbitrary commands with root privileges by inducing a logged-in administrator to visit a malicious website. Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information. |
| CVE-2026-87850 | Medium | 2026-11-18 | Not applicable | No public exploit | nVision sends user's token via query parameters of GET requests. An attacker who obtains valid token can gain access to the victim's account and perform actions on their behalf. This issue was fixed in version 18. |
| CVE-2026-87790 | High | 2026-11-18 | Not applicable | No public exploit | Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote attacker to cause HTTP GET requests from a user's workstation by convincing the user to open a crafted signed eDOC file. Automatic certificate validation retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL and follows redirects without restricting the destination, enabling blind SSRF to loopback and private-network services. Additionally, unrestricted loading of local file URIs (such as file:///dev/zero) causes unbounded memory buffering resulting in Denial of Service (OutOfMemoryError). In automated server verification pipelines with UI:N, impact scales up to CVSS 8.6 High. |
| CVE-2026-87789 | High | 2026-11-18 | Not applicable | No public exploit | Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0 for macOS allows an unauthenticated remote attacker to execute arbitrary commands with the privileges of the current user by convincing the user to open a PDF with a crafted filename and select Send. The application embeds the attachment path in AppleScript source without neutralizing AppleScript syntax, allowing injected do shell script expressions to execute. |
| CVE-2026-86866 | Medium | 2026-11-18 | Not applicable | No public exploit | Tanium addressed a SQL injection vulnerability in multiple products. |
| CVE-2026-86403 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to check whether the calling session originated from an OAuth authorization grant, which allows a third-party application holding a delegated access token to register a new, independent OAuth application under the identity of the delegating user via the OAuth application registration endpoint.. Mattermost Advisory ID: MMSA-2026-00780 |
| CVE-2026-84786 | Unknown | 2026-11-18 | Not applicable | No public exploit | A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records. |
| CVE-2026-82952 | High | 2026-11-18 | Not applicable | No public exploit | Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute for Linux allows an unauthenticated remote attacker to execute arbitrary commands with the privileges of the current user by convincing the user to open and validate a signed PDF with a crafted filename and select Open with Adobe Reader. The application embeds the filename in a sh -c command without neutralizing shell command substitution. |
| CVE-2026-82951 | Medium | 2026-11-18 | Not applicable | No public exploit | Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote attacker to cause HTTP GET requests from a user's workstation by convincing the user to open a crafted signed eDOC file. Automatic certificate validation retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL and follows redirects without restricting the destination, enabling blind SSRF to loopback and private-network services. Additionally, unrestricted loading of local file URIs (such as file:///dev/zero) causes unbounded memory buffering resulting in Denial of Service (OutOfMemoryError). In automated server verification pipelines with UI:N, impact scales up to CVSS 8.6 High. |
| CVE-2026-82171 | High | 2026-11-18 | Not applicable | No public exploit | Dell PowerStore contains an XML External Entity (XXE) Injection vulnerability. A high-privileged attacker could exploit this vulnerability, potentially leading to disclosure of sensitive files and root-level compromise of the appliance. |
| CVE-2026-76516 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the eXtensible ARchive (XAR) GZIP file parser for ClamAV could allow an unauthenticated, remote attacker to exceed the configured MaxFileSize and cause a DoS condition on an affected device. This vulnerability is due to inefficiencies when parsing specifically formatted files with the XAR GZIP file parser. An attacker could exploit this vulnerability by by sending a crafted XAR GZIP file to be scanned. A successful exploit could allow the attacker to effectively cause the ClamAV to exceed the MaxFileSize and potentially get caught in an infinite loop, causing a DoS condition. |
| CVE-2026-76515 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the Object Linking and Embedding, 2nd Generation (OLE2) file parser for ClamAV could allow an unauthenticated, remote attacker to exceed the configured MaxScanTime and cause a DoS condition on an affected device. This vulnerability is due to inefficiencies when parsing specifically formatted files with the OLE2 file parser. An attacker could exploit this vulnerability by by sending a crafted Microsoft Compound File Binary (CFB) file to be scanned. A successful exploit could allow the attacker to effectively cause the ClamAV OLE2 parser to get into an infinite loop, resulting in a DoS condition on the affected software. |
| CVE-2026-76430 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the Ultimate Packer for eXecutables (UPX) unpacker of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper length checks, when unpacking the UPX files, which may result in an out-of-bounds read of heap memory. An attacker could exploit this vulnerability by submitting a crafted UPX for decode. A successful exploit could allow the attacker to cause the ClamAV decode process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-76422 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the debug logging functionality of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper handling of logging values. An attacker could exploit this vulnerability by submitting a file to be scanned by the software that has debug logging enabled. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-76421 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the LZX data algorithm for Microsoft Compiled HTML Help (CHM) file scanning in ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper boundary checks when applying the LZX data algorithm to CHM files during the decoder stage, which may result in buffer overflow. An attacker could exploit this vulnerability by sending a crafted CHM file for scanning. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-76417 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in Object Linking and Embedding, 2nd Generation (OLE2) file parser for ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to logic error when parsing specifically formatted files with the OLE2 file parser. An attacker could exploit this vulnerability by by sending a crafted Microsoft Compound File Binary (CFB) file to be scanned. A successful exploit could allow the attacker to allocate all available memory, causing the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-76416 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the InstallShield file parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to incomplete error checking when the InstallShield File Parser is performing a scan. An attacker could exploit this vulnerability by sending a crafted InstallShield file to be scanned. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate due to an infinite loop, resulting in a DoS condition on the affected software. |
| CVE-2026-76415 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the Yoda'a Crytper (yC) Portable Executable (PE) unpacker of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. . This vulnerability is due to lack of proper error checking for negative values when processing the PE file to be unpacked. An attacker could exploit this vulnerability by sending a PE file to be unpacked. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-76414 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in Microsoft Compiled HTML Help (CHM) file scanning of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to a logic error when scanning the CHM file and following the internal file pointers. An attacker could exploit this vulnerability by sending a crafted CHM file for scanning. A successful exploit could allow the attacker to cause the ClamAV decode process to terminate due to an infinite loop, resulting in a DoS condition on the affected software. |
| CVE-2026-76411 | High | 2026-11-18 | Not applicable | No public exploit | A vulnerability in the phishcheck functionality of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper allocation of memory during processing of URLs. An attacker could exploit this vulnerability by sending a URL to be processed by the software. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. |
| CVE-2026-75795 | Unknown | 2026-11-18 | Not applicable | No public exploit | The Edwiser Bridge WordPress plugin before 4.3.5 does not correctly scope one of its REST API authentication checks, disabling WordPress's REST nonce validation for every route on the site, which allows attackers to make a logged-in administrator perform arbitrary privileged actions, such as creating a new administrator account, via CSRF. |
| CVE-2026-71861 | High | 2026-11-18 | Not applicable | No public exploit | The Chainguard SDK is a public Go SDK for integrating with the Chainguard platform. Prior to 0.1.107, auth/aws.VerifyToken trusts the Chainguard-Audience and Chainguard-Identity headers without requiring those headers to be covered by AWS SigV4 SignedHeaders. An attacker with a fresh STS GetCallerIdentity request signed by a victim can rewrite the unsigned binding headers and replay the proof to another relying party, causing the relying party to authenticate the victim’s AWS identity for an attacker-chosen audience and identity. Code that only uses auth/aws.GenerateToken is unaffected because the generator signs the binding headers, and exploitation requires a signed request within its validity window. This issue is fixed in version 0.1.107. |
| CVE-2026-63189 | Critical | 2026-11-18 | Not applicable | No public exploit | Dialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application’s JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials. This issue is fixed in version 1.11.5. |
| CVE-2026-61583 | High | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40, main/dropbox/dropbox_functions.inc.php accepts a literal .htaccess filename in the course dropbox and stores it in a directory served by Apache, where the file can alter handler behavior under the required AllowOverride All configuration. Any authenticated course participant can upload .htaccess and then upload a PHP payload disguised as a .gif, resulting in code execution as the web-server user when the dropbox tool is enabled. This can expose or modify the Chamilo installation, course content, and database credentials. This issue is fixed in version 1.11.40. |
| CVE-2026-61582 | Medium | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40, main/inc/ajax/user_manager.ajax.php exposes the update_users action without an authorization check and stores attacker-controlled firstname, lastname, and email values without HTML sanitization. An unauthenticated attacker can modify another user's profile fields, and the stored content executes when user_portal.php, the administrative user listing, user information, social profile, course participant list, or message-composer recipient header renders the modified account. Targeting an administrator account can expose administrator-session data or permit actions in that session. This issue is fixed in version 1.11.40. |
| CVE-2026-61578 | High | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40 on the 1.11 release line and in 2.0.0, plugin/cleandeletedfiles/src/ajax.php and public/plugin/CleanDeletedFiles/src/ajax.php pass the request path parameter and list parameter directly to unlink without canonicalization, filename validation, or confinement to the plugin's scanned directories. An authenticated administrator can delete arbitrary files writable by the web server; a cross-site request forgery against an administrator session can reach the same operation. Deleting application source, uploaded content, cache, or configuration files can cause data loss and denial of service. This issue is fixed in version 1.11.40 on the 1.11 release line. No fixed 2.0 release is established as of this review. |
| CVE-2026-61532 | Critical | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.3, src/Chamilo/CourseBundle/Component/CourseCopy/CourseRestorer.php and src/CourseBundle/Component/CourseCopy/CourseRestorer.php use paths supplied by an imported legacy course backup without consistently confining them to the extraction directory. A course teacher can import a crafted backup containing parent-directory path segments, causing file operations to write attacker-controlled content outside the intended destination, including PHP-executable or automatically loaded locations. This can result in code execution as the PHP process and compromise course data, user data, credentials, and the host. This issue is fixed in versions 1.11.40 and 2.0.3. |
| CVE-2026-61528 | High | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. From 2.0.0 until 2.0.3, the BigBlueButton plugin is vulnerable to XML External Entity (XXE) injection when an authenticated administrator configures a malicious BigBlueButton server URL. Processing attacker-controlled XML from that server can read arbitrary local files and perform Server-Side Request Forgery (SSRF). Sensitive configuration, credentials, source code, and internal network resources may be exposed. This issue is fixed in version 2.0.3. |
| CVE-2026-59159 | High | 2026-11-18 | Not applicable | No public exploit | Linux Mint Update Manager manages software updates on Linux Mint systems. From 5.4.8 until 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 6.1.5.1, mint-refresh-cache passes a user-controlled --parent-window-id value directly to the privileged Synaptic process without validating it as an integer. A local user permitted to execute mint-refresh-cache through sudo can inject additional Synaptic command-line options and achieve arbitrary code execution as root. This issue is fixed in versions 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 6.1.5.1. |
| CVE-2026-58320 | Unknown | 2026-11-18 | Not applicable | No public exploit | Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root. This issue affects Apache Iggy: before 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. |
| CVE-2026-5765 | High | 2026-11-18 | Not applicable | No public exploit | The Essential Real Estate plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 5.3.3 via deserialization of untrusted input in the 'saved_search_check_result' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. |
| CVE-2026-55503 | Medium | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.3, main/lp/scormItem.class.php and public/main/lp/scormItem.class.php store an attacker-controlled title element from imsmanifest.xml without cross-site scripting sanitization when a teacher imports a SCORM package. The title reaches c_lp_item.title and is rendered by src/CoreBundle/Resources/views/LearnPath/scorm_list.html.twig through item.title with raw output while Twig auto-escaping is disabled; the default configuration does not apply the optional AI-disclosure sanitization path. Enrolled students or administrators who view the learning-path table of contents can execute the stored content in their browser sessions. This issue is fixed in versions 1.11.40 and 2.0.3. |
| CVE-2026-48728 | Medium | 2026-11-18 | Not applicable | No public exploit | The GLPI Inventory Plugin handles network discovery, inventory, software deployment, and data collection for GLPI agents. Prior to 1.6.8, the /b/deploy, /b/collect, and /b/esx agent API endpoints do not authenticate requests before processing Deploy, Collect, and ESX task operations. An unauthenticated remote attacker can enumerate jobs and manipulate their status through these endpoints, disclosing job information and interfering with task processing. This issue is fixed in version 1.6.8. |
| CVE-2026-45142 | High | 2026-11-18 | Not applicable | No public exploit | Chamilo LMS is an open-source learning management system. Prior to 1.11.40 and 2.0.1, main/lp/lp_ajax_save_objectives.php and public/main/lp/lp_ajax_save_objectives.php trust the request uid parameter instead of the authenticated user identity when saving SCORM learning objectives. Any authenticated student can replace uid with another user's identifier and overwrite that user's objectives because the endpoint performs no ownership check. This issue is fixed in versions 1.11.40 and 2.0.1. |
| CVE-2026-3232 | High | 2026-11-18 | Not applicable | No public exploit | The Easy Appointments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' and 'phone' fields in all versions up to, and including, 3.12.23.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the Customers page. |
| CVE-2026-30502 | Unknown | 2026-11-18 | Not applicable | No public exploit | A Cross-Site Scripting (XSS) vulnerability in OpenKM v6.3.12 allows attackers to execute arbitrary Javascript in the context of the user's browser via a crafted input injected into the Content parameter. |
| CVE-2026-2841 | Medium | 2026-11-18 | Not applicable | No public exploit | The Advanced Custom Fields (ACF) plugin for WordPress is vulnerable to incorrect authorization in all versions up to, and including, 6.7.0. This is due to the 'ACF_Ajax_Query::get_args' method returning the user-supplied ''query' array directly without any key whitelisting or validation. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary query parameters to bypass field-configured role restrictions and exfiltrate sensitive user data including administrator email addresses, login names, and private user metadata via blind oracle techniques. |
| CVE-2026-19707 | Critical | 2026-11-18 | Not applicable | No public exploit | A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1. For an attack to be executable, the Airlock Gateway needs to have 'Smart Form Protection' (or the corresponding expert settings) enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references. The buffer overflow then happens during the parsing of that HTML response. Such a response can come either from a malicious or compromised backend, or from an otherwise trusted backend that returns attacker-supplied HTML, e.g. an application that stores and serves plain user-provided HTML files. Successfully exploiting the vulnerability can enable an attacker to perform a DoS attack or, in the worst case, an RCE attack against the Airlock Gateway in front of the affected backend. Compromising the functionality of the Airlock Gateway could in this way also affect the availability and protection of other well-intentioned backends deployed behind the same Gateway. |
| CVE-2026-19399 | Medium | 2026-11-18 | Not applicable | No public exploit | Improper Authentication and Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ASUS Router firmware allow an unauthenticated nearby user to perform file operations or read files in an unintended directory via crafted HTTP requests during an active user session. Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information. |
| CVE-2026-18643 | Low | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11 fail to enforce the team view permission across all filter combinations of the user listing endpoint which allows an authenticated user to enumerate the membership of a team they are not permitted to view via a crafted request to that endpoint.. Mattermost Advisory ID: MMSA-2026-00755 |
| CVE-2026-18553 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to sanitize terminal escape sequences when rendering server logs via {{mmctl logs}}, which allows an unauthenticated attacker to hijack a system administrator's clipboard or spoof terminal output via a crafted HTTP request whose logged content is later viewed with {{mmctl logs}}. Mattermost Advisory ID: MMSA-2026-00753 |
| CVE-2026-18476 | Low | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11 fail to scope an incoming webhook's direct message target to the webhook's own team, which allows a team administrator to deliver a direct message to a user on a team they have no authority over via a webhook whose posting identity belongs to both teams.. Mattermost Advisory ID: MMSA-2026-00751 |
| CVE-2026-18399 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to enforce the configured GitLab group/namespace restriction on the permalink code-preview feature and the {{get_projects}} MCP tool, which allows an authenticated user with a connected GitLab account to retrieve repository file content or project metadata from projects outside the restricted group via a crafted GitLab permalink or MCP tool call. Mattermost Advisory ID: MMSA-2026-00750 |
| CVE-2026-18396 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to enforce playbook membership management permissions when creating a new playbook which allows a low-privileged user to grant the playbook_admin role to an arbitrary user via a crafted playbook creation request. Mattermost Advisory ID: MMSA-2026-00749 |
| CVE-2026-18079 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 Fail to revoke a user's active sessions when a bulk import links an existing user account to a bot record or changes the account's auth_service/auth_data, which allows an attacker in possession of a session token issued before the import to retain full authenticated access to the affected account via a system administrator-triggered bulk import job.. Mattermost Advisory ID: MMSA-2026-00746 |
| CVE-2026-18075 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to invalidate cached WebSocket session state when an OAuth app is deleted, which allows a revoked OAuth integration to keep receiving real-time events, including private channel posts, via a WebSocket connection that was already open when the app was deleted.. Mattermost Advisory ID: MMSA-2026-00745 |
| CVE-2026-18045 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to enforce the MFA requirement on the update and delete user endpoints, which allows an authenticated user who has not configured MFA to modify or delete their own account via the API despite system-wide MFA enforcement being enabled. Mattermost Advisory ID: MMSA-2026-00744 |
| CVE-2026-17575 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.8.x <= 11.8.5, 11.7.x <= 11.7.10, 11.10.x <= 11.10.2 fails to validate the type of card property fields which allows a board Editor to make a board or card permanently unopenable for all users via a crafted PATCH request storing a non-string property name or value.. Mattermost Advisory ID: MMSA-2026-00743 |
| CVE-2026-17537 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to enforce the channel Access Control Policy's file download permission check when serving file metadata and thumbnails through the drafts, scheduled posts, and post edit history endpoints, which allows an authenticated user who has lost eligibility under the policy to view metadata and thumbnails of file attachments via those endpoints, even though direct file access is correctly denied. Mattermost Advisory ID: MMSA-2026-00740 |
| CVE-2026-16050 | Low | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.7.x <= 11.7.11 fail to sanitize channel mentions when rendering permalinked posts, which allows an authenticated user to discover the display names of private channels they do not have access to via a permalink to a post that mentions the channel.. Mattermost Advisory ID: MMSA-2026-00721 |
| CVE-2026-16021 | Medium | 2026-11-18 | Not applicable | No public exploit | Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to bound the resources consumed while processing an uploaded custom emoji image which allows an authenticated user with default permissions to make the server unresponsive for all users via repeated custom emoji uploads.. Mattermost Advisory ID: MMSA-2026-00720 |
| CVE-2026-15263 | High | 2026-11-18 | Not applicable | No public exploit | A server-side request forgery (SSRF) vulnerability in the Pure Storage FlashArray extension for Windows Admin Center versions could allow an authenticated Gateway User to direct the management gateway to an unintended host, potentially exposing stored FlashArray credentials and API tokens and allowing unauthorized access to the managed FlashArray. |
| CVE-2026-132251 | Low | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token |
| CVE-2026-132250 | Low | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token |
| CVE-2026-132249 | Medium | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible |
| CVE-2026-132248 | Medium | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3 improper authorization allowed project viewers to change project IDs |
| CVE-2026-132247 | Medium | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces |
| CVE-2026-132246 | Medium | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project permissions |
| CVE-2026-132245 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible |
| CVE-2026-132244 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Disk Usage and Build Time pages was possible |
| CVE-2026-132243 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Docker Container Info tab was possible |
| CVE-2026-132242 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Promote build dialog was possible |
| CVE-2026-132241 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE in the .NET build steps auto-discovery was possible |
| CVE-2026-132240 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE via Maven settings file upload was possible |
| CVE-2026-132239 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project viewers to use stored credentials |
| CVE-2026-132238 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.8 disclosure of password parameter values to project viewers was possible |
| CVE-2026-132237 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the external artifact cache |
| CVE-2026-132236 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the pipeline YAML file path |
| CVE-2026-132235 | High | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives |
| CVE-2026-132234 | Critical | 2026-11-18 | Not applicable | No public exploit | In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings |