Overview 266,250 matches · 10,581 in Waratek scope · 977 protected · 3,810 exploited · 1,025 CISA KEV · 5,811 public PoC · 1,610 EPSS ≥ 0.5
266,250matches
10,581in Waratek scope4.0%
977protected0.4%
3,810exploited1.4%
1,025CISA KEV0.4%
5,811public PoC2.2%
1,610EPSS ≥ 0.50.6%
Protected by Waratek
983
0.4%
Rule in development
5
0.0%
Mitigation candidate
163
0.1%
No exploit published
9,430
3.5%
Outside Waratek scope
1,189
0.4%
Not applicable
244,544
91.8%
Withdrawn CVE
9,936
3.7%
Critical
32,026
12.0%
High
101,872
38.3%
Medium
106,826
40.1%
Low
11,429
4.3%
None
79
0.0%
Unknown
14,018
5.3%
split by
peak 37,712 / quarter
Q2 213,445
Protected by Waratek19
Mitigation candidate5
No exploit published98
Outside Waratek scope75
Not applicable2,988
Withdrawn CVE260
Critical394
High1,427
Medium1,287
Low77
Unknown260
blocked by ARMR today19
not blocked3,426
Exploited74
Working exploit published73
Proof of concept only21
Forecast only31
No public exploit3,246
Q3 215,779
Protected by Waratek19
Mitigation candidate8
No exploit published139
Outside Waratek scope53
Not applicable5,350
Withdrawn CVE210
Critical716
High2,412
Medium2,327
Low114
Unknown210
blocked by ARMR today19
not blocked5,760
Exploited132
Working exploit published108
Proof of concept only47
Forecast only44
No public exploit5,448
Q4 215,766
Protected by Waratek40
Mitigation candidate6
No exploit published108
Outside Waratek scope82
Not applicable4,915
Withdrawn CVE615
Critical822
High2,185
Medium2,059
Low85
Unknown615
blocked by ARMR today40
not blocked5,726
Exploited109
Working exploit published95
Proof of concept only65
Forecast only29
No public exploit5,468
Q1 226,316
Protected by Waratek66
Mitigation candidate4
No exploit published250
Outside Waratek scope45
Not applicable5,651
Withdrawn CVE300
Critical1,013
High2,414
Medium2,480
Low109
Unknown300
blocked by ARMR today66
not blocked6,250
Exploited142
Working exploit published187
Proof of concept only264
Forecast only26
No public exploit5,697
Q2 226,429
Protected by Waratek50
Rule in development1
Mitigation candidate7
No exploit published226
Outside Waratek scope82
Not applicable5,980
Withdrawn CVE83
Critical1,177
High2,709
Medium2,387
Low73
Unknown83
blocked by ARMR today50
not blocked6,379
Exploited133
Working exploit published162
Proof of concept only412
Forecast only20
No public exploit5,702
Q3 226,888
Protected by Waratek47
Mitigation candidate6
No exploit published229
Outside Waratek scope90
Not applicable6,111
Withdrawn CVE405
Critical1,182
High2,712
Medium2,470
Low119
Unknown405
blocked by ARMR today47
not blocked6,841
Exploited102
Working exploit published117
Proof of concept only573
Forecast only30
No public exploit6,066
Q4 226,798
Protected by Waratek52
Mitigation candidate3
No exploit published196
Outside Waratek scope52
Not applicable5,925
Withdrawn CVE570
Critical1,069
High2,502
Medium2,571
Low84
Unknown572
blocked by ARMR today52
not blocked6,746
Exploited101
Working exploit published100
Proof of concept only1,519
Forecast only21
No public exploit5,057
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 published142
Outside Waratek scope72
Not applicable10,805
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,215
Forecast only3
No public exploit11,706
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 published150
Proof of concept only5,196
Forecast only2
No public exploit15,274
Q3 2637,712
Protected by Waratek121
Mitigation candidate11
No exploit published3,206
Outside Waratek scope47
Not applicable33,566
Withdrawn CVE761
Critical4,751
High15,836
Medium12,161
Low2,204
None19
Unknown2,741
blocked by ARMR today118
partly blocked3
not blocked37,591
Exploited308
Working exploit published146
Proof of concept only6,502
No public exploit30,756
Q4 2628,366
Protected by Waratek70
Mitigation candidate1
No exploit published1,831
Outside Waratek scope22
Not applicable25,702
Withdrawn CVE740
Critical2,550
High11,540
Medium10,814
Low1,619
None5
Unknown1,838
blocked by ARMR today69
partly blocked1
not blocked28,296
Exploited222
Working exploit published48
Proof of concept only3,772
No public exploit24,324
Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-132808 | Critical | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and low privileges could exploit an Incorrect Authorization vulnerability found in UniFi Access Application to execute arbitrary commands on certain adopted UniFi Access devices. |
| CVE-2026-132807 | Critical | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and under certain conditions could exploit an Improper Certificate Validation vulnerability found in UniFi Access Application to obtain sensitive information from and make unauthorized changes to an adopted UniFi Access device. |
| CVE-2026-132806 | High | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and low privileges could exploit an authenticated SQL Injection vulnerability found in UniFi Access Application to obtain sensitive information and make unauthorized changes within the UniFi Access Application. |
| CVE-2026-132805 | High | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to obtain information and make unauthorized changes on the host device. |
| CVE-2026-132804 | Critical | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to escalate privileges within UniFi OS. |
| CVE-2026-132803 | Critical | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and low privileges could exploit a series of authenticated SQL Injection vulnerabilities found in UniFi Access Application to escalate privileges on the host device. |
| CVE-2026-132802 | Critical | 2026-11-19 | Not applicable | No public exploit | A malicious actor with access to the network and low privileges could exploit an Improper Link Resolution Before File Access vulnerability found in UniFi Access Application to execute arbitrary code with root privileges on the host device. |
| CVE-2026-132798 | High | 2026-11-19 | Not applicable | No public exploit | Improper Limitation of a Pathname to a Restricted Directory in the Como log viewer in Temenos Application Framework Java (TAFJ) R18.SP76.0 allows remote authenticated attackers to read arbitrary files via path traversal |
| CVE-2026-132627 | Medium | 2026-11-19 | Not applicable | No public exploit | A security flaw has been discovered in SourceCodester E-Commerce Shopping Cart Web Application 1.0. Affected by this issue is some unknown functionality of the file action.php. The manipulation of the argument keyword results in sql injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. |
| CVE-2026-132626 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was identified in SourceCodester Modern Ticket Reservation System 1.0. Affected by this vulnerability is an unknown functionality of the file /booking/validate.php. The manipulation of the argument ticket leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. |
| CVE-2026-132625 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was determined in SourceCodester Student Project Allocation and Management System 1.0. Affected is an unknown function of the file /login.php of the component Login Handler. Executing a manipulation of the argument username/password can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. |
| CVE-2026-132622 | Critical | 2026-11-19 | Not applicable | No public exploit | A vulnerability was found in GearUP Hyperev up to 20261020. This impacts the function get_wlan_sitesurvey of the file ld/utils.lua of the component WLAN Site Survey. Performing a manipulation of the argument line results in os command injection. The attack is possible to be carried out remotely. The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2026-132621 | High | 2026-11-19 | Not applicable | No public exploit | A vulnerability has been found in GearUP Hyperev up to 20261020. This affects an unknown function. Such manipulation leads to on-chip debug and test interface with improper access control. The attack can be executed directly on the physical device. The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2026-132611 | Medium | 2026-11-19 | Not applicable | No public exploit | A security vulnerability has been detected in SourceCodester Simple Form Builder Web App 1.0. This impacts the function save_response of the file /classes/Forms.php. The manipulation of the argument q[<index>] leads to unrestricted upload. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. |
| CVE-2026-132610 | Medium | 2026-11-19 | Not applicable | No public exploit | A security flaw has been discovered in SourceCodester Simple Form Builder Web App 1.0. The impacted element is the function save_form of the file /classes/Forms.php. Performing a manipulation of the argument form_code/form_data results in code injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. |
| CVE-2026-132609 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was identified in SourceCodester Online Food Ordering System 1.0. The affected element is an unknown function of the file /web/admin/add_food.php. Such manipulation leads to unrestricted upload. The attack can be launched remotely. The exploit is publicly available and might be used. |
| CVE-2026-132608 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was identified in SECUDOCX DMP up to 9.0.0 Build 1027. This affects an unknown function of the file /DMP/public/login/forward_login.jsp of the component Login. The manipulation of the argument LoginErrorMsg leads to cross site scripting. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2026-132603 | Medium | 2026-11-19 | Not applicable | No public exploit | A flaw has been found in SEO Panel 6.0.0. Affected is an unknown function of the file controllers/siteauditor.ctrl.php of the component Site Auditor. Executing a manipulation of the argument order_col/order_val can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used. Upgrading to version 7.0.0 is able to address this issue. This patch is called 2a2d4aeb718177327b0cd8ce17e2f40328772127. It is suggested to upgrade the affected component. |
| CVE-2026-132602 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was detected in SEO Panel 6.0.0. This impacts an unknown function of the file controllers/siteauditor.ctrl.php of the component Site Auditor. Performing a manipulation of the argument order_col/order_val results in sql injection. The attack can be initiated remotely. The exploit is now public and may be used. Upgrading to version 7.0.0 will fix this issue. The patch is named 389783b5d8235f5637f4e4587f524b5fef07864d. The affected component should be upgraded. |
| CVE-2026-132601 | Medium | 2026-11-19 | Not applicable | No public exploit | A security vulnerability has been detected in SEO Panel 6.0.0. This affects the function mime_content_type of the file controllers/website.ctrl.php of the component Website Import. Such manipulation of the argument website_csv_file leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 7.0.0 mitigates this issue. The name of the patch is 2a2d4aeb718177327b0cd8ce17e2f40328772127. You should upgrade the affected component. |
| CVE-2026-132560 | Medium | 2026-11-19 | Not applicable | No public exploit | A flaw has been found in MemTensor memmy-agent up to 1.1.1. This impacts an unknown function of the file /api/v1/memory/logs of the component Memory HTTP Service. This manipulation causes information disclosure. The attack is restricted to local execution. The exploit has been published and may be used. Patch name: 421ce6cb33861255d34c3887d39aced009b3ce9b. It is suggested to install a patch to address this issue. |
| CVE-2026-132286 | Medium | 2026-11-19 | Not applicable | No public exploit | A security vulnerability has been detected in yangzongzhuan RuoYi up to 4.8.3. The impacted element is an unknown function of the file ruoyi-admin/src/main/java/com/ruoyi/web/controller/system/SysLoginController.java of the component User Registration Endpoint. The manipulation of the argument deptId/status/userId/createBy leads to improper input validation. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The identifier of the patch is d7ad977c9ca64e9b081c893ec56fe08f51f66698. It is recommended to apply a patch to fix this issue. |
| CVE-2026-132283 | Medium | 2026-11-19 | Not applicable | No public exploit | A vulnerability was identified in Directus up to 12.7.0. This issue affects the function AuthenticationService.refresh of the file api/src/services/authentication.ts of the component Authentication Service. Such manipulation leads to session expiration. The attack can be launched remotely. The vendor was contacted early about this disclosure. |
| CVE-2026-132133 | Medium | 2026-11-19 | Not applicable | No public exploit | @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie builds the match regular expression for each path-scoped middleware from its mount path without collapsing duplicate slashes, even when the application enables the ignoreDuplicateSlashes router option. Under that option Fastify's router collapses duplicate slashes in both the registered route and the request path, so a mount path containing a doubled slash is served by the router at its single-slash form while the middleware's compiled match still requires the doubled slash and never matches. A path-scoped middleware such as authentication, authorization, or rate limiting is therefore skipped while the router dispatches the request to the protected handler, without any authentication required. Applications are affected when they enable ignoreDuplicateSlashes and a middleware mount path reaches middie with a duplicate slash, most commonly when a plugin prefix that ends with a slash is joined to a mount path that starts with one. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, and avoid mount paths and plugin prefixes that introduce duplicate slashes. |
| CVE-2026-132131 | High | 2026-11-19 | Not applicable | No public exploit | @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions 8.3.0 through 9.3.6, the internal helper that normalizes a path-scoped middleware's mount path only handles string inputs, but the use method also accepts an array of mount paths and passes it through unchanged, so the normalization silently does nothing. As a result, a trailing slash on an array element survives into the generated route-matching regular expression, and an element that is exactly the root path, meaning a catch-all mount, is dropped entirely. Requests to subroutes of the affected mount paths then skip the path-scoped middleware, such as authentication, authorization, or rate limiting, while Fastify's router still dispatches them to the handler, allowing an unauthenticated client to reach protected routes. Applications are affected when they mount middleware on an array of paths in which an element ends with a slash, including one introduced by a plugin prefix that ends with a slash, or is exactly the root path. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, and avoid array mount paths with a trailing slash element for security relevant middleware. |
| CVE-2026-132129 | Medium | 2026-11-19 | Not applicable | No public exploit | Passing a different column type while using deprecated range predicates, allow OOB read of any memory address. Users should update to 1.17.2 or 1.18.2 |
| CVE-2026-132128 | High | 2026-11-19 | Not applicable | No public exploit | @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie does not honor the router's caseSensitive setting and matches path-scoped middleware mount paths with a case-insensitive regular expression that does not fold non-ASCII characters, while Fastify's router, when caseSensitive is set to false, lowercases the request path with a Unicode-aware conversion that maps the KELVIN SIGN character (U+212A) to the ASCII letter k. A request that spells a k in a protected mount path as the percent-encoded KELVIN SIGN is therefore routed to the protected handler while the middleware mounted on that path, such as authentication, authorization, or rate limiting, never matches and is skipped, letting an unauthenticated client reach the handler. Only applications that set caseSensitive to false and protect a mount path containing the letter k are affected. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, or keep routing case-sensitive, which is the default. |
| CVE-2026-132043 | Medium | 2026-11-19 | Not applicable | No public exploit | In Eclipse Yasson versions 3.0 to 3.0.5, a race condition (CWE-362) exists in the handling of @JsonbNumberFormat. Yasson creates one java.text.NumberFormat instance per annotated property and shares it across all threads that use the same Jsonb instance. NumberFormat is not thread-safe, and the deserializer called parse() on it without synchronization. When multiple threads deserialize concurrently, a thread can receive a numeric value that belongs to another thread's input, receive an incorrect value, or fail with an exception. A remote attacker who can send concurrent requests to an application that deserializes untrusted JSON this way may cause incorrect data to be processed or cause another user's value to be returned. Exploitation requires that the application use @JsonbNumberFormat with a shared Jsonb instance and that the attacker win a timing race. This issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances. |
| CVE-2026-131914 | Critical | 2026-11-19 | Not applicable | No public exploit | Deserialization of untrusted data in double-submit cookie vs. form field validation in Idunno.AntiCsrf versions through 0.9.1 Beta on ASP.NET allows remote unauthenticated attackers to execute code via object injection |
| CVE-2026-130888 | Medium | 2026-11-19 | Not applicable | No public exploit | A flaw was found in nbdkit. The qcow2dec filter's zstd_compressed_cluster() function incorrectly sets the ZSTD input buffer size to the uncompressed cluster size instead of the compressed buffer size. A crafted QCOW2 image with ZSTD-compressed clusters can trigger a heap over-read, leading to a denial of service and potentially exposing heap memory. |
| CVE-2026-129517 | Medium | 2026-11-19 | Not applicable | No public exploit | A cross-site scripting vulnerability exists in Win Bird JYUGYO SHIEN browser extensions for Google Chrome and Microsoft Edge, which allows an attacker to execute arbitrary script in the user's web browser. |
| CVE-2026-129446 | Unknown | 2026-11-19 | Not applicable | No public exploit | The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.4 does not ensure the signature validated on a SAML response covers the element the user identity is read from, allowing unauthenticated attackers to forge a response via signature wrapping and log in as any user, including administrators, when they can supply a single artifact signed by the configured identity provider. |
| CVE-2026-129048 | Critical | 2026-11-19 | Not applicable | No public exploit | Improper Control of Generation of Code ('Code Injection') vulnerability in Jacob N. Breetvelt WP Photo Album Plus wp-photo-album-plus allows Remote Code Inclusion.This issue affects WP Photo Album Plus: from n/a through 9.3.06.003. |
| CVE-2026-129034 | High | 2026-11-19 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Chill Strong Testimonials strong-testimonials allows Stored XSS.This issue affects Strong Testimonials: from n/a through 3.3.18. |
| CVE-2026-129030 | High | 2026-11-19 | Not applicable | No public exploit | Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Mamunur Rashid ShopBuilder – Elementor WooCommerce Builder Addons shopbuilder allows Retrieve Embedded Sensitive Data.This issue affects ShopBuilder – Elementor WooCommerce Builder Addons: from n/a through 3.4.3. |
| CVE-2026-129014 | Medium | 2026-11-19 | Not applicable | No public exploit | Missing Authorization vulnerability in DynamiApps Frontend Admin by DynamiApps acf-frontend-form-element allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Frontend Admin by DynamiApps: from n/a through 3.30.2. |
| CVE-2026-129013 | High | 2026-11-19 | Not applicable | No public exploit | Missing Authorization vulnerability in Deepen Bajracharya Video Conferencing with Zoom video-conferencing-with-zoom-api allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Video Conferencing with Zoom: from n/a through 4.6.12. |
| CVE-2026-129001 | High | 2026-11-19 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Gabe Livan Asset CleanUp: Page Speed Booster wp-asset-clean-up allows Reflected XSS.This issue affects Asset CleanUp: Page Speed Booster: from n/a through 1.4.0.6. |
| CVE-2026-128999 | High | 2026-11-19 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Saphali Saphali Woocommerce Lite saphali-woocommerce-lite allows Stored XSS.This issue affects Saphali Woocommerce Lite: from n/a through 2.0.2. |
| CVE-2026-126631 | High | 2026-11-19 | Not applicable | No public exploit | A flaw was found in OpenSCAP. This vulnerability allows for information disclosure when performing offline scans of untrusted filesystem images, such as container images or virtual machine (VM) disks. Because the scanner does not properly restrict symbolic link (symlink) resolution to the target image's root directory, an attacker can supply a crafted image containing links pointing to files on the host system. When the scan runs, typically with elevated privileges, OpenSCAP follows these links to read sensitive host files and expose their contents in the scan report or manipulate compliance results. |
| CVE-2026-125061 | High | 2026-11-19 | Not applicable | No public exploit | The administration page "Offene Bestellungen" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the customer name of pending orders without output encoding. A registered customer (free self-registration) can submit an HTML-entity-encoded name, which is decoded to markup when the billing address of an order is written. If the PayPal payment is left unfinished, the order is listed on the page and the name is rendered as markup in the browser of an administrator who opens the page. The script code runs with the privileges of that administrator and can, for example, create a new administrator account. Guest orders are not affected, because the name is encoded again. |
| CVE-2026-125060 | High | 2026-11-19 | Not applicable | No public exploit | The checkout of JTL-Shop stores the delivery address ID submitted by the customer in the session and adopts it into the order without verifying that the address belongs to the ordering customer. A remote attacker with access to the checkout, including a guest, can thereby attach the delivery address of another customer to their own order. Name and address of the other customer, and depending on the shop configuration further contact data, then appear in the order confirmation and customer account. As the IDs are sequential, addresses can be enumerated. Goods may also be shipped to the wrong address. |
| CVE-2026-123972 | High | 2026-11-19 | Not applicable | No public exploit | The WP-Slimbox2 Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.1.3.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 a user accesses an injected page. Successful exploitation requires a logged-in user, typically an administrator, to click the attacker's image link in the comment; however, because unmoderated comments appear in the WordPress moderation queue where administrators routinely interact with them, the moderation gate does not meaningfully prevent exploitation. Successful exploitation causes the attacker's own account to receive the complete Administrator role. |
| CVE-2026-123971 | Medium | 2026-11-19 | Not applicable | No public exploit | The Slimbox Plugin plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'el.title (HTML-decoded title attribute of a stored <a rel^=lightbox> element)' parameter in all versions up to, and including, 1.3 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. Exploitation requires a companion plugin such as bbPress that permits low-privileged users to store anchor elements with arbitrary title and rel attributes, as WordPress core comment handling does not preserve rel on anchor tags by default. |
| CVE-2026-123969 | Medium | 2026-11-19 | Not applicable | No public exploit | The Fancy Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.0.0 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. Successful exploitation without administrator interaction requires that the attacker first have one comment approved so that a subsequent payload comment is auto-published; the injected script only executes when a user clicks the malicious image link inside the comment. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-123968 | High | 2026-11-19 | Not applicable | No public exploit | The Slimbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (anchor title within comment HTML)' parameter in all versions up to, and including, 1.0.8 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. WordPress core comment KSES permits unauthenticated commenters to post anchor elements with href and title attributes, so an entity-encoded payload stored in the title attribute survives sanitization verbatim; the browser then decodes the entities when populating the DOM .title property, and the Slimbox library's jQuery .html() caption sink renders it as executable HTML. |
| CVE-2026-123058 | Critical | 2026-11-19 | Not applicable | No public exploit | The web installer of JTL-Shop executes its state-changing installation tasks without checking whether the shop is already installed, and was not removed or locked after the installation. An unauthenticated remote attacker who can reach the installer directory can supply their own database credentials, create administrator and synchronisation accounts and overwrite the shop configuration. This can lead to a full takeover of the shop, including code execution on the server. |
| CVE-2026-121852 | Unknown | 2026-11-19 | Not applicable | No public exploit | The AppPresser WordPress plugin before 5.0.0 does not properly escape the contents of its debug log when displaying it in the admin dashboard, and decodes escape sequences after sanitising input, allowing unauthenticated users to perform Stored XSS attacks against administrators when debug logging is enabled. |
| CVE-2026-120404 | Unknown | 2026-11-19 | No exploit published | No public exploit | The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. An attacker who can supply text that an application analyzes with this name finder can cause high CPU consumption, leading to denial of service. Users are recommended to upgrade to version 2.5.13 or 3.0.0, which fix the issue. |
| CVE-2026-117678 | Medium | 2026-11-19 | Not applicable | No public exploit | Inefficient Algorithmic Complexity vulnerability in benoitc idna allows an attacker who controls a hostname passed to the library to exhaust CPU via an over-long xn-- label. idna:ulabel/1 in src/idna.erl hands every ASCII label that starts with xn-- to punycode:decode/1 without applying check_label_length/1, the 63-octet DNS label limit. punycode:decode/1 in src/punycode.erl builds its output with list appends in insert/4, so its cost grows super-linearly with the label length. A label of a few kilobytes keeps a scheduler busy for seconds to minutes before the label is rejected as invalid punycode. Every decode entry point reaches this path: decode/1, decode/2, to_unicode/1 and from_ascii/1. The encode path reaches it as well, because alabel/1 calls ulabel/1 on an ASCII xn-- label before its own length check, so encode/1, encode/2 and to_ascii/1 are affected for such input. This issue affects idna: from 0.5.0 before 8.0.0. |
| CVE-2026-115677 | High | 2026-11-19 | Not applicable | No public exploit | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in AirTies Kablosuz İletişim Sanayi ve Dış Ticaret A.Ş. Air 5444 allows Overflow Buffers. This issue affects Air 5444: through 2026-11-19. NOTE: The vendor was contacted and it was learned that the product is not supported. |
| CVE-2026-113458 | Medium | 2026-11-19 | Not applicable | No public exploit | Mattermost versions 11.10.x <= 11.10.2, 11.11.x <= 11.11.1, 11.7.x <= 11.7.12 fail to validate the format of configured database connection strings before redacting them, which allows a party with access to a generated Support Packet or server log files to recover plaintext database credentials when the connection string is configured in a non-URL format.. Mattermost Advisory ID: MMSA-2026-00783 |
| CVE-2026-112216 | Medium | 2026-11-19 | Not applicable | No public exploit | Vulnerability involving the exposure of sensitive information in the URLs of the UOC Virtual Campus’s document upload feature. After completing a document upload, the application includes identifiers related to the active session—such as `apjsessionid`—and other internal parameters associated with requests and users in the HTTP GET request parameters. This data may be stored in the browser history and in server or proxy logs, or transmitted via the HTTP Referer header, depending on the configuration and browsing flow. Its inclusion in the URL could allow for the unauthorized disclosure of information to third parties with access to those logs or recipients. |
| CVE-2026-112163 | Medium | 2026-11-19 | Not applicable | No public exploit | Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Kayaport Ödeme Kuruluşu A.Ş. BulutTahsilat – Virtual POS Infrastructure allows Cross-Site Scripting (XSS). This issue affects BulutTahsilat – Virtual POS Infrastructure: through 2026-11-05. |
| CVE-2026-110728 | Medium | 2026-11-19 | Not applicable | No public exploit | The AIKTP plugin for WordPress is vulnerable to Authorization Bypass via Predictable Token in all versions up to, and including, 5.0.7. The vulnerability exists because the plugin's sync token (`aiktpz_token`) is generated using PHP's non-cryptographic `uniqid()` function — producing a wall-clock-derived value with approximately one million microsecond candidates per uncertain generation second — while the unauthenticated, unthrottled REST endpoint `/wp-json/aiktp/checkToken` (registered with `permission_callback => __return_true`) acts as a public brute-force oracle for the token; simultaneously, the capability checks in `check_valid_token` and its wrappers (`verify_aiktp_token_with_edit_capability`, `verify_aiktp_token_with_upload_capability`) inspect only a server-side stored Administrator account (option `aiktp_author`) rather than the actual REST caller, meaning possession of the token alone grants Administrator-equivalent authority to any external request. This makes it possible for unauthenticated attackers to recover the sync token and then invoke `POST /wp-json/aiktp/createpost` to publish arbitrary posts attributed to a site Administrator, `POST /wp-json/aiktp/doUpdatePostWithImageURL` to overwrite the body content of any existing post, and `POST /wp-json/aiktp/doUploadImageToWP` to import remote media and attach it as the featured image of any post. Additionally, when the `aiktpz_token` option has never been initialized, the `checkToken` oracle returns success for an empty token submission due to a loose comparison in `check_valid_token`, providing a zero-effort bypass that requires no brute-forcing whatsoever. |
| CVE-2026-110462 | High | 2026-11-19 | Not applicable | No public exploit | The Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, allows a user authenticated to the web interface with the Installer role to export a system configuration backup. The resulting backup file contains the configured passwords for all privileged roles |
| CVE-2026-110461 | Critical | 2026-11-19 | Not applicable | No public exploit | The Comelit 1456B Multi-User Gateway, in firmware versions up to and including 2.10.0, is configured with static default passwords for multiple privileged roles. None of these passwords are required to be changed during initial configuration, and they remain at their default values unless the administrator changes them manually. An attacker with network access to the device can authenticate using these default credentials and gain administrative control. |
| CVE-2026-110337 | Medium | 2026-11-19 | Not applicable | No public exploit | The Strava datasource plugin's resource handler POST /strava-api forwards a client-supplied endpoint string, and its query parameters, to the Strava API (https://www.strava.com/api/v3/<endpoint>) without validation. When the datasource is not in OAuth pass-through mode, the request is made with the access token stored on the datasource, not the caller's identity. Grafana authorises plugin resource calls only on the datasources:query permission, which Viewers have by default. Any such caller could therefore request any Strava API path the connected account's OAuth grant allows, for example athlete/clubs or routes/{id}, and read the response. The plugin's frontend (stravaApi.ts) only needs a fixed set of paths: athlete, athlete/activities, activities/{id}, activities/{id}/streams and segments/{id}. Requests to Strava are GET only, so the issue is read-only. Affected: plugin versions 1.2.0 through 1.7.2. The fix restricts endpoint to those five patterns and is pending release. The check runs before the access token is resolved, so a rejected request never causes a token refresh or any call to Strava. Paths with .. segments are rejected as well. |
| CVE-2026-109555 | High | 2026-11-19 | Not applicable | No public exploit | The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to PHP Object Injection in all versions up to, and including, 4.17.0 and 6.17.0, respectively, via deserialization of untrusted input during database restore and staging reset. This is due to the database importer treating attacker-controlled text beginning with {WPSTG_BINARY} as trusted internal binary data and decoding its hexadecimal suffix into serialized bytes. This makes it possible for authenticated attackers, with Subscriber-level access and above, to plant a malicious serialized object in their own profile. When an Administrator later performs an ordinary database-including restore or staging reset containing that value, and the restored profile metadata is loaded, either during the restore or in a later request, a built-in POP chain can be used to execute arbitrary code on the server. Additional built-in gadget chains allow arbitrary local file read in both WP STAGING and WP STAGING Pro and arbitrary file deletion in WP STAGING Pro. The attacker does not require Administrator credentials or a copy of a backup, but exploitation does require the later privileged restore or reset. |
| CVE-2026-108687 | Unknown | 2026-11-19 | Not applicable | No public exploit | The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it validates is the same assertion it reads the user identity from, allowing unauthenticated attackers who hold a validly signed assertion for any identity to authenticate as any existing user, including an administrator, through XML signature wrapping. |
| CVE-2026-104357 | Medium | 2026-11-19 | Not applicable | No public exploit | A flaw was found in libtirpc. The SunRPC UDP/datagram server transport reuses a single receive buffer across requests and resets the XDR decode position without rebinding the decode length to the size of the datagram actually received. As a result, when a short UDP RPC request is received after a longer one, the XDR decoder can read stale bytes left in the reused buffer and interpret them as part of the current request, including credential, verifier, or procedure-argument fields. The highest threat from this vulnerability is to data confidentiality and integrity for services that use a UDP-based SunRPC server. |
| CVE-2026-101167 | Medium | 2026-11-19 | Not applicable | No public exploit | Missing Authorization vulnerability in Dataprom Bilişim Teknolojileri LTD. ŞTİ. DataPer Access Control and Security Systems allows Privilege Escalation. This issue affects DataPer Access Control and Security Systems: before v14.15(2026/11). |
| 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-91139 | Medium | 2026-11-18 | Not applicable | No public exploit | Deco BE65 firmware contains a cryptographic weakness in the local web-management authentication flow due to the use of insufficient RSA key sizes. The /login?form=auth endpoint returns a 512-bit RSA public key and sequence value. Successful exploitation may compromise the cryptographic protections applied to local web-management authentication traffic. |
| CVE-2026-91138 | Medium | 2026-11-18 | Not applicable | No public exploit | The Deco BE65 v3 firmware contains a shared hard-coded password hash for the root account in /etc/shadow. Where the corresponding credential is accepted by a production authentication path, an attacker with existing unprivileged shell access may recover or otherwise obtain the plaintext password and use it to escalate privileges. Successful exploitation may grant root-level access to the affected device. |
| 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 |