Overview 406,414 matches · 15,905 in Waratek scope · 0 protected · 5,682 exploited · 1,695 CISA KEV · 25,002 public PoC · 3,845 EPSS ≥ 0.5
406,414matches
15,905in Waratek scope3.9%
0protected0.0%
5,682exploited1.4%
1,695CISA KEV0.4%
25,002public PoC6.2%
3,845EPSS ≥ 0.50.9%
Protected by Waratek
0
0.0%
Rule in development
7
0.0%
Mitigation candidate
412
0.1%
No exploit published
15,486
3.8%
Outside Waratek scope
3,457
0.9%
Not applicable
368,084
90.6%
Withdrawn CVE
18,968
4.7%
Critical
43,638
10.7%
High
157,421
38.7%
Medium
165,930
40.8%
Low
16,310
4.0%
None
79
0.0%
Unknown
23,036
5.7%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
406,414
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 102,415 / year
20062,395
Mitigation candidate1
No exploit published35
Outside Waratek scope14
Not applicable2,332
Withdrawn CVE13
Critical8
High1,215
Medium1,041
Low118
Unknown13
not blocked2,395
Exploited15
Working exploit published1,021
Proof of concept only1
Forecast only3
No public exploit1,355
20076,589
Mitigation candidate13
No exploit published146
Outside Waratek scope66
Not applicable6,284
Withdrawn CVE80
Critical21
High3,159
Medium3,098
Low231
Unknown80
not blocked6,589
Exploited47
Working exploit published2,493
Proof of concept only5
Forecast only5
No public exploit4,039
20085,657
Mitigation candidate11
No exploit published134
Outside Waratek scope51
Not applicable5,429
Withdrawn CVE32
Critical19
High2,843
Medium2,578
Low185
Unknown32
not blocked5,657
Exploited40
Working exploit published2,515
Proof of concept only4
Forecast only9
No public exploit3,089
20095,769
Mitigation candidate16
No exploit published195
Outside Waratek scope45
Not applicable5,467
Withdrawn CVE46
Critical15
High2,731
Medium2,781
Low196
Unknown46
not blocked5,769
Exploited73
Working exploit published2,587
Proof of concept only2
Forecast only3
No public exploit3,104
20104,658
Mitigation candidate14
No exploit published168
Outside Waratek scope74
Not applicable4,374
Withdrawn CVE28
Critical27
High2,091
Medium2,235
Low277
Unknown28
not blocked4,658
Exploited71
Working exploit published1,310
Proof of concept only1
Forecast only9
No public exploit3,267
20114,166
Mitigation candidate13
No exploit published205
Outside Waratek scope83
Not applicable3,843
Withdrawn CVE22
Critical5
High1,783
Medium2,097
Low259
Unknown22
not blocked4,166
Exploited50
Working exploit published689
Proof of concept only4
Forecast only4
No public exploit3,419
20125,340
Mitigation candidate24
No exploit published291
Outside Waratek scope76
Not applicable4,886
Withdrawn CVE63
Critical18
High1,722
Medium3,029
Low508
Unknown63
not blocked5,340
Exploited54
Working exploit published831
Proof of concept only7
Forecast only46
No public exploit4,402
20135,297
Mitigation candidate18
No exploit published318
Outside Waratek scope284
Not applicable4,540
Withdrawn CVE137
Critical22
High1,723
Medium2,901
Low514
Unknown137
not blocked5,297
Exploited90
Working exploit published517
Proof of concept only2
Forecast only21
No public exploit4,667
20147,967
Mitigation candidate13
No exploit published292
Outside Waratek scope233
Not applicable7,349
Withdrawn CVE80
Critical20
High1,929
Medium5,282
Low656
Unknown80
not blocked7,967
Exploited95
Working exploit published791
Proof of concept only12
Forecast only14
No public exploit7,055
20156,562
Mitigation candidate7
No exploit published308
Outside Waratek scope171
Not applicable5,975
Withdrawn CVE101
Critical47
High2,346
Medium3,481
Low587
Unknown101
not blocked6,562
Exploited93
Working exploit published643
Proof of concept only16
Forecast only19
No public exploit5,791
20166,455
Mitigation candidate9
No exploit published479
Outside Waratek scope108
Not applicable5,791
Withdrawn CVE68
Critical871
High2,876
Medium2,419
Low221
Unknown68
not blocked6,455
Exploited95
Working exploit published420
Proof of concept only26
Forecast only28
No public exploit5,886
201718,005
Mitigation candidate15
No exploit published701
Outside Waratek scope212
Not applicable13,606
Withdrawn CVE3,471
Critical2,074
High6,566
Medium5,663
Low231
Unknown3,471
not blocked18,005
Exploited198
Working exploit published1,247
Proof of concept only51
Forecast only23
No public exploit16,486
201817,971
Mitigation candidate23
No exploit published724
Outside Waratek scope205
Not applicable15,375
Withdrawn CVE1,644
Critical2,564
High7,498
Medium6,109
Low156
Unknown1,644
not blocked17,971
Exploited224
Working exploit published1,064
Proof of concept only81
Forecast only33
No public exploit16,569
201918,812
Rule in development1
Mitigation candidate30
No exploit published796
Outside Waratek scope262
Not applicable16,090
Withdrawn CVE1,633
Critical2,615
High7,189
Medium7,082
Low293
Unknown1,633
not blocked18,812
Exploited312
Working exploit published779
Proof of concept only116
Forecast only50
No public exploit17,555
202019,065
Mitigation candidate38
No exploit published943
Outside Waratek scope263
Not applicable16,921
Withdrawn CVE900
Critical2,737
High7,716
Medium7,324
Low388
Unknown900
not blocked19,065
Exploited325
Working exploit published597
Proof of concept only150
Forecast only66
No public exploit17,927
202121,826
Rule in development1
Mitigation candidate28
No exploit published669
Outside Waratek scope331
Not applicable18,996
Withdrawn CVE1,801
Critical2,805
High8,723
Medium8,108
Low389
Unknown1,801
not blocked21,826
Exploited474
Working exploit published442
Proof of concept only210
Forecast only165
No public exploit20,535
202226,216
Rule in development1
Mitigation candidate20
No exploit published902
Outside Waratek scope269
Not applicable23,666
Withdrawn CVE1,358
Critical4,367
High10,260
Medium9,850
Low379
Unknown1,360
not blocked26,216
Exploited462
Working exploit published562
Proof of concept only2,746
Forecast only92
No public exploit22,354
202330,786
Mitigation candidate38
No exploit published882
Outside Waratek scope205
Not applicable27,528
Withdrawn CVE2,133
Critical4,974
High11,566
Medium11,795
Low317
Unknown2,134
not blocked30,786
Exploited554
Working exploit published555
Proof of concept only5,560
Forecast only107
No public exploit24,010
202440,596
Mitigation candidate28
No exploit published621
Outside Waratek scope186
Not applicable39,010
Withdrawn CVE751
Critical4,837
High15,285
Medium18,979
Low736
None1
Unknown758
not blocked40,596
Exploited734
Working exploit published400
Proof of concept only7,448
Forecast only82
No public exploit31,932
202549,867
Rule in development4
Mitigation candidate23
No exploit published731
Outside Waratek scope139
Not applicable47,148
Withdrawn CVE1,822
Critical4,454
High16,643
Medium23,006
Low3,035
None10
Unknown2,719
not blocked49,867
Exploited714
Working exploit published591
Proof of concept only10,971
Forecast only16
No public exploit37,575
2026102,415
Mitigation candidate30
No exploit published5,946
Outside Waratek scope180
Not applicable93,474
Withdrawn CVE2,785
Critical11,138
High41,557
Medium37,072
Low6,634
None68
Unknown5,946
not blocked102,415
Exploited962
Working exploit published471
Proof of concept only19,605
Forecast only5
No public exploit81,372
20062008201020122014201620182020202220242026
| 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 |