Overview 140,064 matches · 6,383 in Waratek scope · 445 protected · 816 exploited · 169 CISA KEV · 3,317 public PoC · 389 EPSS ≥ 0.5
140,064matches
6,383in Waratek scope4.6%
445protected0.3%
816exploited0.6%
169CISA KEV0.1%
3,317public PoC2.4%
389EPSS ≥ 0.50.3%
Protected by Waratek
446
0.3%
Rule in development
2
0.0%
Mitigation candidate
96
0.1%
No exploit published
5,839
4.2%
Outside Waratek scope
1,945
1.4%
Not applicable
131,736
94.1%
Withdrawn CVE
0
0.0%
split by
peak 36,330 / year
20153,052
Protected by Waratek18
Mitigation candidate1
No exploit published145
Outside Waratek scope102
Not applicable2,786
Medium3,052
blocked by ARMR today18
not blocked3,034
Exploited22
Working exploit published195
Proof of concept only6
Forecast only7
No public exploit2,822
20162,446
Protected by Waratek25
Mitigation candidate4
No exploit published292
Outside Waratek scope51
Not applicable2,074
Medium2,446
blocked by ARMR today25
not blocked2,420
not established1
Exploited16
Working exploit published122
Proof of concept only6
Forecast only9
No public exploit2,293
20175,687
Protected by Waratek24
Mitigation candidate5
No exploit published326
Outside Waratek scope124
Not applicable5,208
Medium5,687
blocked by ARMR today24
not blocked5,663
Exploited18
Working exploit published332
Proof of concept only21
Forecast only2
No public exploit5,314
20186,163
Protected by Waratek51
Mitigation candidate8
No exploit published428
Outside Waratek scope177
Not applicable5,499
Medium6,163
blocked by ARMR today51
not blocked6,112
Exploited38
Working exploit published348
Proof of concept only27
Forecast only7
No public exploit5,743
20197,117
Protected by Waratek35
Mitigation candidate14
No exploit published405
Outside Waratek scope263
Not applicable6,400
Medium7,117
blocked by ARMR today34
partly blocked1
not blocked7,082
Exploited47
Working exploit published297
Proof of concept only30
Forecast only9
No public exploit6,734
20207,359
Protected by Waratek35
Mitigation candidate15
No exploit published496
Outside Waratek scope286
Not applicable6,527
Medium7,359
blocked by ARMR today35
not blocked7,324
Exploited58
Working exploit published197
Proof of concept only37
Forecast only10
No public exploit7,057
20218,137
Protected by Waratek29
Mitigation candidate11
No exploit published291
Outside Waratek scope259
Not applicable7,547
Medium8,137
blocked by ARMR today29
not blocked8,108
Exploited86
Working exploit published240
Proof of concept only90
Forecast only44
No public exploit7,677
20229,908
Protected by Waratek58
Mitigation candidate3
No exploit published570
Outside Waratek scope211
Not applicable9,066
Medium9,908
blocked by ARMR today58
not blocked9,850
Exploited73
Working exploit published270
Proof of concept only953
Forecast only34
No public exploit8,578
202311,824
Protected by Waratek29
Mitigation candidate10
No exploit published440
Outside Waratek scope144
Not applicable11,201
Medium11,824
blocked by ARMR today29
not blocked11,795
Exploited97
Working exploit published237
Proof of concept only2,408
Forecast only26
No public exploit9,056
202418,998
Protected by Waratek19
Mitigation candidate5
No exploit published320
Outside Waratek scope149
Not applicable18,505
Medium18,998
blocked by ARMR today19
not blocked18,979
Exploited129
Working exploit published114
Proof of concept only3,597
Forecast only10
No public exploit15,148
202523,043
Protected by Waratek37
Rule in development2
Mitigation candidate14
No exploit published471
Outside Waratek scope83
Not applicable22,436
Medium23,043
blocked by ARMR today37
not blocked23,006
Exploited127
Working exploit published170
Proof of concept only5,244
Forecast only5
No public exploit17,497
202636,330
Protected by Waratek86
Mitigation candidate6
No exploit published1,655
Outside Waratek scope96
Not applicable34,487
Medium36,330
blocked by ARMR today86
not blocked36,244
Exploited105
Working exploit published116
Proof of concept only6,767
No public exploit29,342
201520162017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-98100 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can import documents in the HWP format, including pictures that link to an external file. An out-of-bounds read existed when the link target of a crafted picture was read, so memory past the picture data could end up in the converted document. In fixed versions the link target is taken only from the picture data. |
| CVE-2026-97999 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Base documents can hold an embedded HSQLDB database. When the experimental features option is enabled, LibreOffice offers to migrate such a database to the embedded Firebird engine when the document is opened. A heap buffer overflow existed when binary values were copied during the migration, because a value could be longer than the space set aside for its column. In fixed versions that space is enlarged whenever a value is longer than its column. |
| CVE-2026-97894 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Calc can open spreadsheets in the DIF format, and text files such as CSV in the UTF-16 encoding. Both are read one line at a time. An out-of-bounds read existed when a line of a crafted file was read, because the length of the line could be miscalculated, so memory beyond the line could be copied into the imported document. In fixed versions each line is read up to its limit and no further. |
| CVE-2026-97892 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice checks the digital signatures of a PDF document when the document is opened, and shows whether each signature is valid. An out-of-bounds write existed when a signature was checked, because the parts of the file that a crafted signature claims to cover were not checked against the size of the file. In fixed versions a signature that claims to cover anything outside the file is reported as not valid. |
| CVE-2026-91114 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, PermissionCheckboxSetField accepts permission codes that the field did not offer and stores them without an allowlist, then renders permission codes without escaping them. A user with access to the Security section can save attacker-controlled content as a permission code, causing JavaScript to execute in the browser of another user who views the field. This issue is fixed in version 6.2.13. |
| CVE-2026-91113 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit a record through a GridField detail form can submit a user-controlled ClassName value to change the record into an unrelated class without the create and edit permission checks required for that target class. This permits an unauthorized record type change outside the GridField's intended model hierarchy. This issue is fixed in version 6.2.13. |
| CVE-2026-91112 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a user with CMS_ACCESS_SecurityAdmin but without ADMIN can edit or reparent a group that grants ADMIN-equivalent permissions through an assigned role or a parent group, thereby escalating to full administrative privileges. This issue is fixed in version 6.2.13. |
| CVE-2026-91110 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not normalize certain control bytes that browsers ignore when parsing URLs. A CMS author can place those bytes before a javascript: URL in stored content so the sanitiser misses the dangerous scheme, and JavaScript executes in the browser of another user who views the content. This issue is fixed in version 6.2.13. |
| CVE-2026-88989 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit records through a GridField detail form can send a direct save request that creates a new record even when the user does not have permission to create that record type. The server-side save path checks edit access but does not enforce the required create permission before persistence. This issue is fixed in version 6.2.13. |
| CVE-2026-88988 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove SVG data URIs from stored CMS content even though SVG documents can execute script. A CMS author can save such content, and JavaScript executes in the browser of another user who views it. This issue is fixed in version 6.2.13. |
| CVE-2026-88987 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove script-capable XHTML and XML data URIs from stored CMS content. A CMS author can save such content, and JavaScript executes in the browser of another user who views it. This issue is fixed in version 6.2.13. |
| CVE-2026-88019 | Medium | 2026-11-16 | No exploit published | No public exploit | When Apache Shiro is used with the Jakarta EE integration module, the automatic form saving feature weakens the security of a form that is resubmitted after login. Cookies set by the application during the resubmission could lose their security attributes, such as `Secure` and `SameSite`. In addition, the resubmitted form data and cookies could be sent to an untrusted host. This issue affects Apache Shiro from 2.0.0-alpha through 3.0.1, only when using `shiro-jakarta-ee` integration module with form saving enabled (the default). Mitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely. Alternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form. |
| CVE-2026-87932 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Writer can save documents in DOCX format. A document can contain content controls whose values are bound to custom XML data, and that data is updated with the current values when the document is exported, including in a conversion run from the command line. Values taken from the document were not escaped where they were used, so a crafted document could write a file of its choosing anywhere the user can write when it was exported to DOCX. In fixed versions these values are written into the document directly, and the XSLT transformations LibreOffice runs can no longer write files or use the network. |
| CVE-2026-85240 | Medium | 2026-11-16 | Not applicable | No public exploit | Mattermost Desktop App versions <=6.3 6.0.3 6.3.2.0 fail to handle filesystem errors that can occur when finalizing certain file downloads, which allows a malicious or compromised server to cause a denial of service by crashing the entire desktop application via a specially crafted download Mattermost Advisory ID: MMSA-2026-00779 |
| CVE-2026-84234 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can open PDF files in Draw, where the PDF import converts each page into drawing objects that can be edited. Images in the PDF, including images with a transparency mask, are converted along the way. An out-of-bounds write existed when an image with a transparency mask was converted, because positions taken from a crafted image were not checked against the size of the image buffer. In fixed versions the image size is limited, and the position of each mask pixel is checked before it is written. |
| CVE-2026-74763 | Medium | 2026-11-16 | No exploit published | No public exploit | Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies. Annotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules. In addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected. This issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared. Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence. Alternatively, declare authorization annotations directly on each protected implementing method. |
| CVE-2026-74762 | Medium | 2026-11-16 | No exploit published | No public exploit | Apache Shiro is vulnerable to session fixation when a user is authenticated via the "Remember me" functionality. In affected versions, when a subject is restored from a "Remember me" cookie, the existing session is not invalidated, nor is a new session created with a new ID. Additionally, session IDs were accepted from the request URL even when session ID URL rewriting was disabled. This issue affects all Apache Shiro versions through 3.0.0, only when RememberMe functionality is enabled. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by invalidating the existing session and creating a new session with a new ID when a subject is restored from a "Remember me" cookie, and by ignoring session IDs in the URL when URL rewriting is disabled. |
| CVE-2026-64890 | Medium | 2026-11-16 | Not applicable | No public exploit | : Cleartext Storage of Sensitive Information vulnerability in Johnson Controls Open Blue Companion Android App on Android allows : Retrieve Embedded Secrets from Software. This issue affects Open Blue Companion Android App: before R2.22.0. |
| CVE-2026-63246 | Medium | 2026-11-16 | Not applicable | No public exploit | A kernel pool buffer overflow vulnerability in the ct0531fl.sys file of the Creative WDM Audio Driver (64-bit), Sound Blaster Audigy 4 and Sound Blaster Audigy 5/Rx could allow a local attacker with low privilege access to cause a denial of service. |
| CVE-2026-32789 | Medium | 2026-11-16 | Not applicable | No public exploit | An out-of-bounds read vulnerability exists in VideoLAN VLC 3.0.23. By using a specially crafted NUV file, an attacker could exploit this vulnerability to perform an out-of-bounds read, potentially leading to the disclosure of sensitive information. |
| CVE-2026-28731 | Medium | 2026-11-16 | Not applicable | No public exploit | A memory corruption vulnerability exists in VideoLAN VLC 3.0.23. A specially crafted Interplay MVE file can trigger a condition that allows access to a variable that is not explicitly initialized, which under certain conditions can lead to code execution in the context of the current process. |
| CVE-2026-21177 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Settings Suggestions prior to One UI 8.5 allows local attackers to automatically launch an application in the background. User interaction is required for triggering this vulnerability. |
| CVE-2026-21174 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass APK verification. |
| CVE-2026-21173 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to initiate an unauthorized APK restoration. |
| CVE-2026-21172 | Medium | 2026-11-16 | Not applicable | No public exploit | Incomplete cleanup in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to establish an unauthorized connection. |
| CVE-2026-21171 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper initialization in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass user authorization. User interaction is required for triggering this vulnerability. |
| CVE-2026-21170 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper enforcement of behavioral workflow in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to write arbitrary files with Smart Switch privilege. |
| CVE-2026-21169 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Smart Switch prior to version 3.7.74.1 allows adjacent attackers to install arbitrary applications. User interaction is required for triggering this vulnerability. |
| CVE-2026-21168 | Medium | 2026-11-16 | Not applicable | No public exploit | External control of system or configuration setting in Smart Switch prior to version 3.7.74.7 allows local attackers to bypass required user interaction. |
| CVE-2026-21166 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authentication in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to install arbitrary applications. |
| CVE-2026-21165 | Medium | 2026-11-16 | Not applicable | No public exploit | Insufficient session expiration in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass device authentication. User interaction is required for triggering this vulnerability. |
| CVE-2026-21164 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper handling of insufficient permission in Samsung Pay for Galaxy Watch prior to version 8.0.53 allows local attackers to install arbitrary applications. |
| CVE-2026-21163 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Bixby prior to version 4.1.20 allows remote attackers to launch arbitrary activity with Bixby privilege. |
| CVE-2026-21162 | Medium | 2026-11-16 | Not applicable | No public exploit | Out-of-bounds write in libiosotglib.so prior to version 3.7.73.4 allows physical attackers to execute arbitrary code. User interaction is required for triggering this vulnerability. |
| CVE-2026-21161 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Samsung Members prior to version 5.8.20.31 allows local attackers to launch arbitrary activity with Samsung Members privilege. |
| CVE-2026-21160 | Medium | 2026-11-16 | Not applicable | No public exploit | Cross-site request forgery in Samsung Health prior to version 7.1.0.053 allows remote attackers to access sensitive information. User interaction is required for triggering this vulnerability. |
| CVE-2026-21159 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in Samsung Pass prior to version 5.2.12.7 allows physical attackers to access sensitive information. |
| CVE-2026-21158 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper certificate validation in CP prior to SMR Nov-2026 Release 1 allows local privileged attackers to bypass SIM lock. |
| CVE-2026-21156 | Medium | 2026-11-16 | Not applicable | No public exploit | Out-of-bounds write in libsmkvextractor.so prior to SMR Nov-2026 Release 1 allows local attackers to write out-of-bounds memory. |
| CVE-2026-21155 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Out-of-bounds write in bootloader prior to SMR Nov-2026 Release 1 allows physical attackers to write out-of-bounds memory. |
| CVE-2026-21154 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in libsecuibc.so prior to SMR Nov-2026 Release 1 allows local attackers to access dump data. |
| CVE-2026-21150 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in edmnativehelper prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-21149 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in StatusBarManagerService prior to SMR Nov-2026 Release 1 allows local attackers to use the privileged APIs. |
| CVE-2026-21148 | Medium | 2026-11-16 | Not applicable | No public exploit | Incorrect authorization in Samsung Messages prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-21147 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivity in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21146 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivitySmall in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21145 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivityLarge in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21144 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in RecentsCallLogLargeWidgetProvider in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21143 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in CoverScreenRecentsWidgetProvider in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21141 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in Samsung Dialer prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-18566 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can import EMF, EMF+ and WMF images, which may be embedded in documents. Several out-of-bounds reads existed in the readers for these formats, because sizes, counts and offsets taken from a crafted image were not checked against the data the image actually holds. In fixed versions these values are checked against the size of each record and the data that remains, and a record that fails the checks is not used. |
| CVE-2026-18564 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can export documents to PDF protected by a password. With the PDF 2.0 option the file is encrypted with 256-bit AES, using a file encryption key and salts that are meant to be random. The key and the salts were drawn from a pseudo-random number generator that is not suitable for cryptography, so the encryption key of an exported PDF could be recovered without knowing the password. In fixed versions the key and the salts are drawn from the random source of the operating system. |
| CVE-2026-18563 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice supports fonts embedded in documents. When a document is exported to PDF, the fonts it uses are embedded in the PDF, and a font in CFF (Compact Font Format) is converted to another font format on the way. An out-of-bounds write existed when the charstring program of a crafted font was interpreted, because some indexes and ranges taken from the font were not checked against the size of the data they refer to. In fixed versions these indexes and ranges are checked, and a font that fails the checks is not converted. |
| CVE-2026-129954 | Medium | 2026-11-16 | Not applicable | No public exploit | NodePress through 8.5.1 contains an HTML injection vulnerability in linesToEmailContent() that allows unauthenticated attackers to inject markup into notification emails because comment content is not escaped. Attackers can post comments or replies via POST /comments containing forged links, images, or tracking resources rendered in administrator and author mail clients from the blog's address. |
| CVE-2026-129953 | Medium | 2026-11-16 | Not applicable | No public exploit | NodePress through 8.5.1 contains a rate limit bypass vulnerability that allows unauthenticated attackers to evade throttling by spoofing the X-Forwarded-For header, because trustProxy is enabled. Attackers can send X-Forwarded-For set to 127.0.0.1 or rotate values to brute-force the administrator password via POST /admin/login and evade comment IP blocklists. |
| CVE-2026-129951 | Medium | 2026-11-16 | Not applicable | No public exploit | Rowy through 3.0.0 contains a stored cross-site scripting vulnerability that allows authenticated users with table write access to inject scripts via URL field links lacking scheme validation. Attackers can store values like javascript: URIs containing the string http in URL cells, executing script when victims click the open-link button to steal Firebase sessions. |
| CVE-2026-129950 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rowy through 3.0.0 contains an incorrect permission assignment vulnerability in default Firebase Storage rules that grants any user holding a role read and write access to the entire bucket. Authenticated users restricted to a single table or read-only access can use the Firebase SDK directly to list, download, overwrite, and delete any stored files. |
| CVE-2026-129949 | Medium | 2026-11-16 | Not applicable | No public exploit | Rowy through 3.0.0 contains a stored cross-site scripting vulnerability that allows authenticated users with table write access to inject unsanitized HTML into Markdown cells. Attackers can store iframe, object, or form elements with javascript: URLs that execute when administrators view the table, stealing Firebase sessions. |
| CVE-2026-129946 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a stored cross-site scripting vulnerability in the DocumentRenderer component that allows authenticated content editors to inject scripts via unvalidated link href values. Editors can paste anchors with javascript: URLs into document fields, executing script when visitors click rendered links and stealing the keystatic-gh-access-token cookie. |
| CVE-2026-129945 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker's GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker's GitHub identity. |
| CVE-2026-129944 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a path traversal vulnerability in the getIsPathValid function that allows unauthenticated remote attackers to access sibling paths sharing a content directory name prefix. Attackers can send requests with a no-cors header to the blob, update, and tree handlers under /api/keystatic to read, create, overwrite, or delete files such as posts-evil/pwn.yaml. |
| CVE-2026-129942 | Medium | 2026-11-16 | Not applicable | No public exploit | Prime CMS (@primecms/core) through 0.4.0-beta.0 contains a missing authentication vulnerability that allows unauthenticated attackers to invoke privileged GraphQL mutations because the @Authorized() decorator is omitted. Attackers can call updateWebhook, createRelease, unpublishDocument and updateUser at /prime/graphql to create releases and, with a record UUID, redirect webhooks, unpublish documents, or overwrite user profiles. |
| CVE-2026-129940 | Medium | 2026-11-16 | Not applicable | No public exploit | Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an open redirect vulnerability in the unauthenticated GET /prime/redirect route that allows remote attackers to redirect users to external sites. Attackers can craft links with a 36-character id and arbitrary url parameter on the trusted Prime host to send victims to phishing sites. |
| CVE-2026-129887 | Medium | 2026-11-16 | Not applicable | No public exploit | thirdweb Dashboard through commit 940b3745 contains an information disclosure vulnerability that allows authenticated users to read non-public team metadata by requesting the team join page with any invite ID. Attackers who know a team slug can obtain the serialized Team object, exposing billing email, billing status, Stripe customer ID, verified domain and support identifiers. |
| CVE-2026-129886 | Medium | 2026-11-16 | Not applicable | Proof of concept only | thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in revalidatePathAction and revalidateCacheTagAction server actions in revalidate.ts. Unauthenticated attackers can use action identifiers exposed in the client bundle to send POST requests that purge cached pages and data, forcing repeated regeneration and degrading performance. |
| CVE-2026-129885 | Medium | 2026-11-16 | Not applicable | No public exploit | Unrolled Secure before 1.18.0 contains an SSLRedirect bypass vulnerability in Secure.isSSL() that trusts the client-supplied r.URL.Scheme to determine HTTPS transport. Attackers can send plaintext HTTP requests with an absolute-form https:// request-target to skip the HTTPS redirect and have application responses served unencrypted. |
| CVE-2026-129884 | Medium | 2026-11-16 | Not applicable | No public exploit | thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in the fetchClientSecret Next.js server action that allows unauthenticated attackers to create Stripe checkout sessions for other teams. Attackers can invoke the action with a forged Team object containing a victim's stripeCustomerId to obtain Growth plan Checkout session client secrets with attacker-influenced return URLs. |
| CVE-2026-129883 | Medium | 2026-11-16 | Not applicable | No public exploit | thirdweb Dashboard through commit 940b3745 contains an open redirect vulnerability that allows remote attackers to send users to arbitrary sites by supplying an unvalidated redirectUri parameter on the /pay/[id] payment link page. Attackers can distribute payment links with a malicious redirectUri that PayPageWidget opens via window.open after payment without noopener, enabling phishing and reverse tabnabbing of the payment page. |
| CVE-2026-129882 | Medium | 2026-11-16 | Not applicable | No public exploit | Kiwi TCMS before 17.1 contains a hard-coded cryptographic key vulnerability that allows remote attackers to forge signed data by using the publicly known Django SECRET_KEY in tcms/settings/common.py. Attackers can forge or tamper with signed cookie-based messages and django.core.signing payloads, weakening password-reset and session-authentication HMACs on deployments keeping the default. |
| CVE-2026-129881 | Medium | 2026-11-16 | Not applicable | No public exploit | Weblate 2026.6 through 2026.11.2 contains an information disclosure vulnerability in ChangeManager.last_changes() that exposes workspaces the viewer cannot view by skipping Workspace.can_view() checks site-wide. Anonymous visitors on instances with REQUIRE_LOGIN disabled and only public projects can query /changes/, /api/changes/, or RSS/CSV feeds to obtain hidden workspace names, UUIDs, actions, and timestamps. |
| CVE-2026-129876 | Medium | 2026-11-16 | Not applicable | No public exploit | OfficeCLI 1.0.56 through 1.0.161 contains a stored cross-site scripting vulnerability in the officecli watch preview that allows attackers to inject script via unescaped numbering w:color values. Attackers can craft a DOCX whose color closes the style element, then abuse the unauthenticated /api/batch endpoint to read local files and modify the watched document. |
| CVE-2026-129871 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rocboss paopao-ce through 0.6.0-alpha.3 contains a payment bypass vulnerability that allows unauthenticated attackers to obtain paid attachments by reading storage URLs from the GET /v1/post endpoint. Attackers can download the paid file directly from the unauthenticated LocalOSS /oss static route, whose signed URL expired parameter is never checked. |
| CVE-2026-129869 | Medium | 2026-11-16 | Not applicable | No public exploit | SamWaf 1.0.128 through 1.3.25-beta.11 contains a request body inspection bypass vulnerability in WafEngine.ServeHTTP that skips bodies with chunked encoding or lengths of 2048 bytes or more. Remote unauthenticated attackers can send SQL injection, XSS, command injection, traversal or upload payloads chunked or padded, which reach the protected backend uninspected. |
| CVE-2026-129867 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rocboss paopao-ce through 0.6.0-alpha.3 contains a stored cross-site scripting vulnerability that allows registered users to inject script by abusing #topic link wrapping in preparePost and parsePostTag. Attackers can publish posts or comments with a crafted topic containing a lone '<' and event handler to steal the PAOPAO_TOKEN JWT from localStorage and take over viewer accounts. |
| CVE-2026-129866 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Dinky through 1.2.5 contains a missing authorization vulnerability in ClusterConfigurationController that allows authenticated users without cluster configuration permissions to list Flink cluster configurations. Attackers can query the /api/clusterConfiguration/list and listAll endpoints to retrieve full configJson deployment settings for every cluster in their tenant. |
| CVE-2026-129862 | Medium | 2026-11-16 | Not applicable | No public exploit | Koillection before 1.8.6 contains an information disclosure vulnerability that allows unauthenticated attackers to view objects nested under private parents through the shared search autocomplete route. Attackers can query GET /user/{username}/search/autocomplete/{term}, whose native SQL filters on visibility instead of final_visibility, to obtain names, ids and counts of hidden collections, items, albums and wishlists. |
| CVE-2026-129861 | Medium | 2026-11-16 | Not applicable | No public exploit | @tinacms/graphql 2.2.2 through 4.1.0 contains a path traversal vulnerability that allows authenticated users to write files outside the content root by following pre-existing dangling symlinks. Attackers can create documents through the GraphQL API targeting a dangling symlink, bypassing assertWithinBase checks, to write controlled content such as authorized_keys to server-writable locations. |
| CVE-2026-129860 | Medium | 2026-11-16 | Not applicable | No public exploit | Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.7 contain a reachable assertion vulnerability in ParsePFDEntry() that allows attackers to abort applications via an invalid orientation tag. Attackers can supply a crafted JPEG XR file with an out-of-range WMP_tagTransformation value to crash applications using default assertion-enabled builds, or store an unchecked orientation value otherwise. |
| CVE-2026-129859 | Medium | 2026-11-16 | Not applicable | No public exploit | Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.1 contain a NULL pointer dereference vulnerability in ImageStrDecDecode() in image/decode/strdec.c. Attackers can supply a crafted JPEG XR file declaring a colour format with no channels, leaving p1MBbuffer[0] NULL and crashing the decoder via memset. |
| CVE-2026-129858 | Medium | 2026-11-16 | Not applicable | No public exploit | Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.6 contain a stack buffer over-read vulnerability in ReadWMIHeader() in image/decode/strdec.c due to an unterminated signature buffer. Attackers can supply a crafted JPEG XR file whose 8 signature bytes contain no zero byte, causing strstr to read past the stack buffer and potentially crash the application. |
| CVE-2026-129856 | Medium | 2026-11-16 | Not applicable | No public exploit | wallabag 2.3.3 before 2.6.16 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through article author metadata rendered with Twig raw in entry.html.twig. Attackers can embed HTML event handlers in a web page's author metadata so scripts run in a victim's wallabag session when the saved entry is opened, exposing their data. |
| CVE-2026-129852 | Medium | 2026-11-16 | Not applicable | No public exploit | SeaweedFS before 4.42 contains an information disclosure vulnerability that allows unauthenticated attackers to probe local files by supplying a filesystem path in gcs_google_application_credentials. Attackers can send crafted gRPC FetchAndWriteNeedle requests and use differing error messages to learn file existence, readability, and partial content shape on the host. |
| CVE-2026-129851 | Medium | 2026-11-16 | Not applicable | Proof of concept only | SeaweedFS before 4.42 contains a server-side request forgery vulnerability in the VolumeServer.FetchAndWriteNeedle gRPC method that allows unauthenticated attackers to bypass the incomplete CVE-2026-73080 fix. Attackers can supply crafted replicas[].url entries or an azure_endpoint to make the volume server send requests with controlled tokens and bodies to internal services and metadata addresses. |
| CVE-2026-129706 | Medium | 2026-11-16 | Not applicable | No public exploit | In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation. The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application. The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely. |
| CVE-2026-129553 | Medium | 2026-11-16 | Not applicable | No public exploit | Tensei through 0.11.5 contains an open redirect vulnerability in the @tensei/social-auth SocialAuthCallbackController that allows unauthenticated attackers to redirect users by supplying an unvalidated clientCallback query parameter. Attackers can craft links to the /:provider/callback route that send victims to attacker-controlled sites for phishing and leak the issued temporary access token appended after login. |
| CVE-2026-129551 | Medium | 2026-11-16 | Not applicable | No public exploit | Tensei through 0.11.5 contains a prototype pollution vulnerability in parseSortFromStringToObject of @tensei/rest that allows unauthenticated attackers to set Object.prototype properties via the sort parameter. Attackers can send a sort value like __proto__.<name>:<value> to list, fetch-one, update or delete routes before authorization, altering application logic and causing denial of service. |
| CVE-2026-129549 | Medium | 2026-11-16 | Not applicable | No public exploit | Tensei through 0.11.5 contains an unrestricted file upload vulnerability in the @tensei/media plugin that allows unauthenticated attackers to upload dangerous file types via the files/upload route. Attackers can set the multipart Content-Type to upload HTML or SVG files served from the application origin, causing stored cross-site scripting and storage consumption. |
| CVE-2026-129548 | Medium | 2026-11-16 | Not applicable | No public exploit | Kalmia through 0.2.0 contains a stored cross-site scripting vulnerability that allows read-only authenticated users to upload HTML or SVG files via the upload-file endpoint without type restrictions. Attackers can share links to files served unauthenticated through the file get route, executing JavaScript in the admin origin to steal administrator JWTs from localStorage. |
| CVE-2026-129543 | Medium | 2026-11-16 | Not applicable | No public exploit | Access of resource using incompatible type ('type confusion') vulnerability in Samsung Open Source Starfish allows Input Data Manipulation. |
| CVE-2026-129541 | Medium | 2026-11-16 | Not applicable | No public exploit | EdgeChat 2.5.0 through 2.21.0 contains a cross-site scripting vulnerability that allows invited users to inject HTML through unescaped usernames in the Vditor @-mention autocomplete. Attackers can register with a username containing an img onerror payload that executes when mentioned, stealing the localStorage session token to take over victim accounts. |
| CVE-2026-129492 | Medium | 2026-11-16 | Not applicable | No public exploit | Bolo (bolo-solo) 1.7 through 2.6.4 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts via the unsanitized commentOriginalCommentName parameter. Attackers can post a comment to /article/comments with a short payload that steals non-HttpOnly session cookies from visitors, enabling takeover of administrator accounts. |
| CVE-2026-129491 | Medium | 2026-11-16 | Not applicable | No public exploit | Qbian61 forum-java commit 20f7e68 through commit 63152c4 contains a stored cross-site scripting vulnerability that allows authenticated users to inject script by posting unsanitized comment content rendered via jQuery .html() in the reply dialog. Attackers can post comments with img onerror payloads that execute when victims click Reply, stealing the non-HttpOnly sid session cookie to hijack accounts including administrators. |
| CVE-2026-129307 | Medium | 2026-11-16 | Not applicable | No public exploit | eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4. |
| CVE-2026-129306 | Medium | 2026-11-16 | Not applicable | No public exploit | libspdm is a sample implementation that follows the DMTF SPDM specifications. Prior to 3.8.3 and 4.0.0-rc2, libspdm_x509_verify_cert_chain() in os_stub/cryptlib_openssl/pk/x509.c and os_stub/cryptlib_mbedtls/pk/x509.c validates certificate signatures one link at a time instead of validating the complete X.509 path. In deployments using a pinned root with a constrained multi-tier PKI, an attacker holding a valid issuer credential below a constrained CA can present a subordinate certificate that exceeds pathLenConstraint or nameConstraints and may be accepted for SPDM identity validation. Exploitation requires the application to use libspdm's backend validation without an additional certificate-chain validation mechanism, the pinned root cannot be substituted, and the deployment's measurement policy must allow identity impersonation alone to satisfy its acceptance requirements. The mbedTLS backend remains unable to enforce nameConstraints because upstream mbedTLS does not implement that check. The full-chain validation changes are released in versions 3.8.3 and 4.0.0-rc2. |
| CVE-2026-129301 | Medium | 2026-11-16 | Not applicable | No public exploit | mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3. |
| CVE-2026-129300 | Medium | 2026-11-16 | Not applicable | No public exploit | mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.7.0 until 4.6.3, receiveds_format() in src/mailparser/utils.py catches only TypeError and ValueError while converting the trailing date of an attacker-controlled Received header. An out-of-range year can cause calendar.timegm() to raise OverflowError, and a sufficiently large timezone offset can cause datetime.fromtimestamp() to raise OSError. These exceptions are outside the MailParserError hierarchy, so one crafted header can abort the entire message parse through every parse_from_* entry point and may drop a queued batch. This issue is fixed in version 4.6.3. |
| CVE-2026-129299 | Medium | 2026-11-16 | Not applicable | No public exploit | mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, multiple message-processing behaviors can raise exceptions or silently lose content. Headers colliding with methods such as Parse, Message, and Write_Attachments can place bound method objects into parsed output and raise TypeError when a caller requests JSON serialization such as mail_json. When byte input is parsed through parse_from_bytes(), an 8-bit header value returned as email.header.Header can likewise raise TypeError when an X_raw accessor passes the value to json.dumps; both exceptions are outside the MailParserError hierarchy. Separately, rewritten names such as Subject_json and X_Spam_Flag can be substituted or disappear from mail, headers, and JSON output while has_defects remains false, and a headerless message can be treated as falsy before parser state is initialized, causing body and attachment properties to return empty values without an error signal. These behaviors can abort message processing or hide malicious indicators from downstream scanners. This issue is fixed in version 4.6.2. |
| CVE-2026-129296 | Medium | 2026-11-16 | Not applicable | No public exploit | mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.8.0 until 4.6.0, the write_attachments() and write_sample() APIs use attacker-controlled attachment filenames without sufficient sanitization and path containment validation. Directory traversal sequences and absolute filesystem paths can cause an attachment to be written outside the intended output directory. An attacker can overwrite files accessible to the parsing process when an application extracts attachments from a crafted message. This issue is fixed in version 4.6.0. |
| CVE-2026-129239 | Medium | 2026-11-16 | Not applicable | No public exploit | Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.3.1, Directus allows an authenticated non-admin with update permission on directus_shares to modify user_created, role, item, and collection on an existing owned share because authorization checks the pre-update row and does not revalidate the merged row. The update path does not force user_created to the acting user or rerun share access checks when item or collection changes. Setting user_created and role to administrator identifiers causes guest share authentication to derive administrator accountability from both fields, exposing data reachable from the shared item beyond the owner and share role permissions. The issue requires update permission on directus_shares, an item the account can share, and knowledge of administrator user and role identifiers, and it does not issue an administrator token or provide write or availability impact. This issue is fixed in version 12.3.1. |
| CVE-2026-129237 | Medium | 2026-11-16 | Not applicable | No public exploit | qbee-agent is the device agent component of the qbee.io IoT device management platform. Prior to 2026.41, the unpackTar extraction logic in app/utils/tar.go validates cleaned archive entry paths with strings.HasPrefix(targetPath, destdirClean) without enforcing a path-separator boundary. When UseContext enables the Docker Compose build context path in app/configuration/bundle_docker_compose.go, a less-privileged archive supplier with delegated configuration and/or file-manager access can provide a sibling-prefix traversal entry that passes the check, causing utils.UnpackTar to create directories and regular files outside the intended context extraction directory with qbee-agent process privileges, despite the supplier lacking authority to write those sibling files. In deployments where only full device or fleet administrators can provide Docker Compose context archives, this behavior is hardening rather than a crossed security boundary. The demonstrated impact is limited to nearby cache or project paths sharing the destination prefix, may affect integrity or availability of qbee-agent-managed Docker Compose state, and does not establish arbitrary absolute-path writes or direct code execution. This issue is fixed in version 2026.41. |