Overview 334,991 matches · 15,536 in Waratek scope · 1,368 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
334,991matches
15,536in Waratek scope4.6%
1,368protected0.4%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
1,369
0.4%
Rule in development
0
0.0%
Mitigation candidate
7
0.0%
No exploit published
14,160
4.2%
Outside Waratek scope
4,374
1.3%
Not applicable
296,213
88.4%
Withdrawn CVE
18,868
5.6%
Critical
33,382
10.0%
High
129,349
38.6%
Medium
138,549
41.4%
Low
10,722
3.2%
None
71
0.0%
Unknown
22,918
6.8%
blocked by ARMR today
1,368
0.4%
partly blocked
1
0.0%
not blocked
333,622
99.6%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
334,991
100.0%
split by
peak 80,310 / year
20063,897
Protected by Waratek4
No exploit published98
Outside Waratek scope40
Not applicable3,711
Withdrawn CVE44
Critical8
High1,427
Medium2,027
Low391
Unknown44
blocked by ARMR today4
not blocked3,893
No public exploit3,897
20074,044
Protected by Waratek5
No exploit published134
Outside Waratek scope71
Not applicable3,757
Withdrawn CVE77
Critical11
High1,720
Medium2,034
Low202
Unknown77
blocked by ARMR today5
not blocked4,039
No public exploit4,044
20083,091
Protected by Waratek2
No exploit published120
Outside Waratek scope67
Not applicable2,875
Withdrawn CVE27
Critical13
High1,311
Medium1,585
Low155
Unknown27
blocked by ARMR today2
not blocked3,089
No public exploit3,091
20093,109
Protected by Waratek5
No exploit published181
Outside Waratek scope53
Not applicable2,830
Withdrawn CVE40
Critical8
High1,256
Medium1,642
Low163
Unknown40
blocked by ARMR today5
not blocked3,104
No public exploit3,109
20103,271
Protected by Waratek4
No exploit published161
Outside Waratek scope73
Not applicable3,007
Withdrawn CVE26
Critical16
High1,304
Medium1,677
Low248
Unknown26
blocked by ARMR today4
not blocked3,267
No public exploit3,271
20113,422
Protected by Waratek3
No exploit published178
Outside Waratek scope108
Not applicable3,114
Withdrawn CVE19
High1,363
Medium1,794
Low246
Unknown19
blocked by ARMR today3
not blocked3,419
No public exploit3,422
20124,408
Protected by Waratek6
No exploit published278
Outside Waratek scope79
Not applicable3,987
Withdrawn CVE58
Critical11
High1,369
Medium2,496
Low474
Unknown58
blocked by ARMR today6
not blocked4,402
No public exploit4,408
20134,683
Protected by Waratek16
Mitigation candidate1
No exploit published304
Outside Waratek scope277
Not applicable3,968
Withdrawn CVE117
Critical13
High1,415
Medium2,647
Low491
Unknown117
blocked by ARMR today16
not blocked4,667
No public exploit4,683
20147,087
Protected by Waratek32
No exploit published282
Outside Waratek scope249
Not applicable6,455
Withdrawn CVE69
Critical9
High1,526
Medium4,856
Low627
Unknown69
blocked by ARMR today32
not blocked7,055
No public exploit7,087
20155,817
Protected by Waratek25
No exploit published285
Outside Waratek scope190
Not applicable5,221
Withdrawn CVE96
Critical32
High1,928
Medium3,208
Low553
Unknown96
blocked by ARMR today25
not blocked5,792
No public exploit5,817
20165,926
Protected by Waratek39
No exploit published464
Outside Waratek scope125
Not applicable5,234
Withdrawn CVE64
Critical795
High2,559
Medium2,293
Low215
Unknown64
blocked by ARMR today39
not blocked5,887
No public exploit5,926
201716,567
Protected by Waratek80
No exploit published680
Outside Waratek scope234
Not applicable12,113
Withdrawn CVE3,460
Critical1,707
High5,857
Medium5,314
Low229
Unknown3,460
blocked by ARMR today79
partly blocked1
not blocked16,487
No public exploit16,567
201816,729
Protected by Waratek154
No exploit published697
Outside Waratek scope312
Not applicable13,928
Withdrawn CVE1,638
Critical2,236
High6,960
Medium5,743
Low152
Unknown1,638
blocked by ARMR today154
not blocked16,575
No public exploit16,729
201917,650
Protected by Waratek94
No exploit published754
Outside Waratek scope479
Not applicable14,694
Withdrawn CVE1,629
Critical2,332
High6,651
Medium6,735
Low303
Unknown1,629
blocked by ARMR today94
not blocked17,556
No public exploit17,650
202018,054
Protected by Waratek124
Mitigation candidate1
No exploit published888
Outside Waratek scope463
Not applicable15,683
Withdrawn CVE895
Critical2,441
High7,264
Medium7,057
Low397
Unknown895
blocked by ARMR today124
not blocked17,930
No public exploit18,054
202120,631
Protected by Waratek95
No exploit published623
Outside Waratek scope453
Not applicable17,660
Withdrawn CVE1,800
Critical2,504
High8,263
Medium7,677
Low387
Unknown1,800
blocked by ARMR today95
not blocked20,536
No public exploit20,631
202222,522
Protected by Waratek167
Mitigation candidate1
No exploit published831
Outside Waratek scope364
Not applicable19,811
Withdrawn CVE1,348
Critical3,459
High8,767
Medium8,578
Low368
Unknown1,350
blocked by ARMR today167
not blocked22,355
No public exploit22,522
202324,123
Protected by Waratek113
Mitigation candidate1
No exploit published726
Outside Waratek scope228
Not applicable20,930
Withdrawn CVE2,125
Critical3,412
High9,248
Medium9,056
Low281
Unknown2,126
blocked by ARMR today113
not blocked24,010
No public exploit24,123
202432,005
Protected by Waratek72
No exploit published556
Outside Waratek scope215
Not applicable30,415
Withdrawn CVE747
Critical3,092
High12,384
Medium15,148
Low627
None1
Unknown753
blocked by ARMR today72
not blocked31,933
No public exploit32,005
202537,645
Protected by Waratek68
No exploit published646
Outside Waratek scope132
Not applicable34,984
Withdrawn CVE1,815
Critical2,918
High13,482
Medium17,497
Low1,026
None10
Unknown2,712
blocked by ARMR today68
not blocked37,577
No public exploit37,645
202680,310
Protected by Waratek261
Mitigation candidate3
No exploit published5,274
Outside Waratek scope162
Not applicable71,836
Withdrawn CVE2,774
Critical8,365
High33,295
Medium29,485
Low3,187
None60
Unknown5,918
blocked by ARMR today261
not blocked80,049
No public exploit80,310
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-97639 | Medium | 2026-11-17 | Not applicable | No public exploit | The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.14 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to activate any already-installed inactive plugin on the site. |
| CVE-2026-97187 | High | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes due to incorrect authorization in workspaces. |
| CVE-2026-86676 | High | 2026-11-17 | Not applicable | No public exploit | A post-authentication command injection vulnerability in the “Description” parameter of a CGI program in Zyxel DX3300-T0 firmware versions through 5.50(ABVY.8.3)C0 could allow an authenticated attacker with administrator privileges to execute OS commands by sending a crafted HTTP request. |
| CVE-2026-86061 | High | 2026-11-17 | Not applicable | No public exploit | Teable is an AI spreadsheet for business. Prior to release.2026-07-17T05-20-38Z.2264, the routes for PluginService::regenerateSecret and PluginService::delete carry no @Permissions decorator, and the methods omit plugin ownership checks. An authenticated attacker can directly target another plugin's identifier to rotate and disclose its OAuth secret or delete the plugin, including system plugins. Separately, PermissionGuard authorizes several nested API requests using a caller-controlled parent tableId, baseId, or spaceId, while the services resolve the requested child object only by its globally unique identifier. An authenticated attacker can provide a parent resource the attacker owns together with a victim's child identifier. ViewService::getViewById can then disclose another tenant's view configuration, embedded filter values, field layout, and shareId. DashboardService::updatePluginStorage and the view-position updatePluginStorage path can overwrite another tenant's plugin storage because the plugin installation is not rebound to the authorized base, dashboard, table, or view. This issue is fixed in release.2026-07-17T05-20-38Z.2264. |
| CVE-2026-85778 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to run code in protected pipelines through a scheduled pipeline execution policy after the policy had been unassigned due to incorrect authorization checks. |
| CVE-2026-84987 | Medium | 2026-11-17 | Not applicable | No public exploit | code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Prior to 9.23.0, an authenticated attacker can call the autocomplete API with a request endpoint that contains the configured remote endpoint only as a substring. The endpoint validation uses an unanchored regular expression, so a different internal route can satisfy the check and be invoked server-side through the autocomplete request. The vulnerable path uses SharpFormAutocompleteRemoteField::setRemoteEndpoint(); applications using SharpFormAutocompleteRemoteField::setRemoteCallback() are not affected by this endpoint-selection flaw. This issue is fixed in version 9.23.0. |
| CVE-2026-84974 | Medium | 2026-11-17 | Not applicable | No public exploit | code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Prior to 9.23.0, an authenticated attacker can submit an arbitrary PHP class name through the embed_key parameter to multiple embed API endpoints. The application passes the selected class to the Laravel service container, which invokes the class's __construct() method and recursively instantiates constructor dependencies, potentially causing unauthorized integrity or availability effects. The attacker cannot supply constructor parameter values or invoke an arbitrary method. This issue is fixed in version 9.23.0. |
| CVE-2026-82025 | High | 2026-11-17 | Not applicable | No public exploit | WP File Manager before 8.0.7 contains a file upload restriction bypass vulnerability that allows authenticated administrators to upload arbitrary PHP files by exploiting a misconfigured elFinder connector in file_folder_manager.php where an empty uploadDeny list causes allowPutMime() to unconditionally return true, bypassing the uploadAllow restriction. Attackers can upload a .php file directly or upload it under an allowed filename and then rename it via the rename connector command, achieving remote code execution as the web server user. |
| CVE-2026-80322 | High | 2026-11-17 | Not applicable | No public exploit | Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests. |
| CVE-2026-79614 | Critical | 2026-11-17 | Not applicable | No public exploit | An out-of-bounds write vulnerability in “libclinkc.so” in Zyxel DX3301-T0/EX3301-T0 firmware versions through 5.50(ABVY.8.3)C0 could allow an unauthenticated attacker to elevate privileges and potentially execute arbitrary commands by sending a crafted HTTP request. WAN access is disabled by default on these devices. |
| CVE-2026-77224 | High | 2026-11-17 | Not applicable | No public exploit | Camunda 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 contains an XML External Entity (XXE) injection vulnerability in the camunda-external-task-client's DomXmlDataFormat.defaultDocumentBuilderFactory(), which fails to disable external entity resolution when parsing object variables serialized with application/xml. An attacker able to write a process variable can trigger arbitrary file read and out-of-band outbound HTTP requests from every worker JVM that deserializes the variable, enabling exfiltration of credentials, service-account tokens, and private key material from network segments deeper than the engine itself. |
| CVE-2026-67455 | High | 2026-11-17 | Not applicable | No public exploit | NVIDIA Model Optimizer for Linux and Windows contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, denial of service, and information disclosure. |
| CVE-2026-65167 | Medium | 2026-11-17 | Not applicable | No public exploit | NVIDIA TensorRT contains a vulnerability where a user could cause memory allocation with excessive size value by crafting a malicious TRT engine. A successful exploit of this vulnerability might lead to denial of service. |
| CVE-2026-65132 | High | 2026-11-17 | Not applicable | No public exploit | NVIDIA Megatron-LM contains a vulnerability in checkpoint loading where an attacker could cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, information disclosure, and data tampering. |
| CVE-2026-65106 | High | 2026-11-17 | Not applicable | No public exploit | NVIDIA Transformer Engine for Linux contains a vulnerability where a user could cause deserialization by loading untrusted data. A successful exploit of this vulnerability might lead to code execution, information disclosure, and denial of service. |
| CVE-2026-62267 | High | 2026-11-17 | Not applicable | No public exploit | matrix-hookshot is a Matrix bot for connecting to external services like GitHub, GitLab, JIRA, and more. Prior to 7.3.3, Hookshot can crash in src/Bridge.ts while processing a modern Matrix reply whose m.relates_to.m.in_reply_to.event_id identifies an event that the bot cannot read. Bridge event handling calls botClient.getEvent() for the parent event without catching the resulting M_NOT_FOUND error, allowing the rejected request to escape reply processing and terminate the service. This issue is fixed in version 7.3.3. |
| CVE-2026-35190 | Unknown | 2026-11-17 | Not applicable | No public exploit | Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group. Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service. CWE: CWE-125: Out-of-bounds Read Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present. Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code. A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data. FIPS impact: no The affected code is outside the FIPS module boundary. |
| CVE-2026-21609 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Improper Authorization vulnerability was introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was reported via our Bug Bounty program. |
| CVE-2026-21607 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21607 was introduced in versions 10.3.26 and 11.3.12. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to disclose protected web application files outside the intended resource location, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Jira Software Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 See the release notes (https://confluence.atlassian.com/jirasoftware/jira-software-data-center-release-notes.html). You can download the latest version of Jira Software Data Center from the Jira Data Center Download Archives (https://www.atlassian.com/software/jira/download-archives). |
| CVE-2026-21606 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21606 was introduced in versions 10.3.26 and 11.3.12. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to disclose protected resources outside declared resource directories, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Jira Software Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 See the release notes (https://confluence.atlassian.com/jirasoftware/jira-software-data-center-release-notes.html). You can download the latest version of Jira Software Data Center from the Jira Data Center Download Archives (https://www.atlassian.com/software/jira/download-archives). |
| CVE-2026-21605 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21605 was introduced in versions 2.0.0, 3.0.0, 4.0.0, 5.0.0, 6.0.1, 6.1.0, 6.2.0, 6.3.1, 6.4.0, 6.5.0, 6.6.0 ,6.7.0, 6.8.0, 6.9.0, 6.10.0, 6.11.0, 6.12.0, 6.13.0, 6.14.0, 6.15.1, 7.0.1, 7.1.0, 7.2.0, 7.3.1, 7.4.0, 7.5.0, 7.6.0, 7.7.2, 7.8.0, 7.9.0, 7.11.0, 7.12.0, 7.13.0, 7.14.0, 7.15.0, 7.16.0, 7.17.0, 7.18.0, 7.19.0, 7.20.0, 8.0.0, 8.1.0, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 8.7.1, 8.8.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0, 10.2.0, and 11.0.0 of Confluence Data Center. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Confluence Data Center and Server customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Confluence Data Center 11.0: Upgrade to a release greater than or equal to 11.0.1 Confluence Data Center 10.2: Upgrade to a release greater than or equal to 10.2.20 Confluence Data Center 9.2: Upgrade to a release greater than or equal to 9.2.27 See the release notes ([https://confluence.atlassian.com/doc/confluence-release-notes-327.html]). You can download the latest version of Confluence Data Center and Server from the download center ([https://www.atlassian.com/software/confluence/download-archives]). The following description summarizes the vulnerability reported internally: Confluence CssServlet forwards a request-controlled path to ServletRequest.getRequestDispatcher. The dispatcher URL-decodes and normalizes the path, allowing an unauthenticated attacker to use an encoded traversal sequence to access protected web application resources such as /WEB-INF/web.xml. The demonstrated impact is disclosure of protected files that may contain configuration or secrets; no integrity or availability impact was demonstrated. |
| CVE-2026-21603 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. This Stored XSS vulnerability, with a CVSS Score of 8.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser. Atlassian recommends that Jira Core Data Center and Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Penetration Testing program. |
| CVE-2026-21602 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. This Stored XSS vulnerability, with a CVSS Score of 7.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser. Atlassian recommends that Jira Core Data Center and Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Penetration Testing program. |
| CVE-2026-21601 | High | 2026-11-17 | Not applicable | No public exploit | This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0 and 11.0.0 of Jira Service Management Data Center. This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 8.7, allows an unauthenticated attacker to perform actions as another user. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was discovered by Nagli and reported via our Bug Bounty program |
| CVE-2026-21600 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Security Misconfiguration vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This Security Misconfiguration vulnerability, with a CVSS Score of 8.9, allows an authenticated attacker to to get into the system utilizing loopholes exposed from security best-practices being overlooked. Atlassian recommends that Bamboo Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 13.0: Upgrade to a release greater than or equal to 13.0.1 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). This vulnerability was reported via our Atlassian (Internal) program. |
| CVE-2026-21599 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21599 was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N allows an authenticated attacker to expose assets in your environment susceptible to exploitation. Atlassian recommends that Bamboo Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 13.0: Upgrade to a release greater than or equal to 13.0.1 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 See the release notes (https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html). You can download the latest version of Bamboo Data Center from the download center (https://www.atlassian.com/software/bamboo/download-archives). |
| CVE-2026-21598 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21598 was introduced in versions 10.2.0, 11.0.0, 12.0.0 and 12.1.0. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to potentially disclose sensitive information from the deployed Bamboo web application root, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Bamboo Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). |
| CVE-2026-21596 | High | 2026-11-17 | Not applicable | No public exploit | This High severity SSTI (Server-side Template Injection) vulnerability known as CVE-2026-21596 was introduced in version 12.0.0, 12.1.0. This SSTI (Server-side Template Injection) vulnerability, with a CVSS Score of 7.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N allows an authenticated attacker to execute arbitrary commands, which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires no user interaction. Atlassian recommends that Bamboo Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to the specified supported fixed version: Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). |
| CVE-2026-21595 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Improper Authorization vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.6, allows an unauthenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Bamboo Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 13.0: Upgrade to a release greater than or equal to 13.0.1 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). This vulnerability was reported via our Penetration Testing program. |
| CVE-2026-21594 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21594 was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to disclose protected files from the Bamboo web application root, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Bamboo Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 See the release notes (https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html). You can download the latest version of Bamboo Data Center from the download center (https://www.atlassian.com/software/bamboo/download-archives). |
| CVE-2026-21593 | High | 2026-11-17 | Not applicable | No public exploit | This High severity OS Command Injection vulnerability known as CVE-2026-21593 was introduced in version 4.9.0. This OS Command Injection vulnerability, with a CVSS Score of 7.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N allows an authenticated attacker to execute arbitrary commands. Atlassian recommends that Fisheye and Crucible Data Center and Server customers upgrade to the latest version. If you are unable to do so, upgrade your instance to the specified supported fixed version: Fisheye and Crucible 4.9: Upgrade to a release greater than or equal to 4.9.16 See the Fisheye release notes (https://confluence.atlassian.com/fisheye/fisheye-release-notes-965552419.html) and Crucible release notes (https://confluence.atlassian.com/crucible/crucible-releases-298977378.html). You can download the latest version of Fisheye and Crucible from the Crucible Download Archives (https://www.atlassian.com/software/crucible/download-archives). |
| CVE-2026-21592 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21592 was introduced in version 4.9.0. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 7.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P allows an unauthenticated attacker to disclose protected application configuration files, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction. Atlassian recommends that Crucible Server customers upgrade to the latest version. If you are unable to do so, upgrade your instance to the specified supported fixed version: Crucible Server 4.9: Upgrade to a release greater than or equal to 4.9.16 See the Crucible Server release notes ([https://confluence.atlassian.com/crucible/crucible-releases-298977378.html]). You can download the latest version of Crucible from the Crucible Download Archives ([https://www.atlassian.com/software/crucible/download-archives]). The following description summarizes the vulnerability reported via our Penetration Testing program: Crucible do not account for path parameters when validating protected paths requested through the static-resource route. A crafted path segment passes validation, after which Jetty removes the path parameter during dispatch and resolves the request to a protected resource. This can expose files under WEB-INF and permit direct invocation of admin-area JSPs outside the normal interceptor and administrative password checks. An ordinary authenticated user can exploit the issue, and unauthenticated exploitation is possible when anonymous access is enabled. |
| CVE-2026-21591 | High | 2026-11-17 | Not applicable | No public exploit | This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This PrivEsc (Privilege Escalation) vulnerability, with a CVSS Score of 7.4, allows an authenticated attacker to perform actions as a higher-privileged user. Atlassian recommends that Bamboo Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.26 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.13 Bamboo Data Center 13.0: Upgrade to a release greater than or equal to 13.0.1 See the release notes ([https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html]). You can download the latest version of Bamboo Data Center from the download center ([https://www.atlassian.com/software/bamboo/download-archives]). This vulnerability was reported via our Penetration Testing program. |
| CVE-2026-21590 | High | 2026-11-17 | Not applicable | No public exploit | This High severity Information Path Traversal (Arbitrary Read/Write) vulnerability was introduced in versions 9.12.0, 10.3.0, and 11.3.0 of Jira Software Data Center. This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7, allows a remote unauthenticated attacker to read files from the Jira web application root. Atlassian recommends that Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Software Data Center 9.12: Upgrade to a release greater than or equal to 9.12.40 Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.26 Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.12 See the release notes (https://confluence.atlassian.com/jirasoftware/jira-software-data-center-release-notes.html). You can download the latest version of Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Bug Bounty program. |
| CVE-2026-18491 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user holding a granular personal access token with limited scope to authorize Kubernetes API proxy access beyond the token's intended boundaries due to missing granular scope enforcement in the Kubernetes agent proxy-user authorization flow. |
| CVE-2026-18241 | High | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to access protected CI/CD variables and resources due to a race condition in pipeline job authorization. |
| CVE-2026-16609 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with owner-role permissions to execute arbitrary JavaScript in another user's browser through the Confluence integration due to improper input validation. |
| CVE-2026-16545 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.10 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an unauthenticated user to read private project metadata from packages published by other projects due to incorrect authorization checks. |
| CVE-2026-130804 | Unknown | 2026-11-17 | Not applicable | No public exploit | The microcontroller lacks enabled debug lock bits, leaving the physical Single-Wire (SWS) debugging interface completely unrestricted. This allows an attacker with physical access to use a hardware programmer to dump the entire production firmware. |
| CVE-2026-130803 | Unknown | 2026-11-17 | Not applicable | No public exploit | The firmware and flash memory store critical cryptographic secrets, such as global AES keys and network master keys, in unencrypted formats. Additionally, active session tokens (Store Pairing Tokens) are written to the flash in plaintext, exposing live network credentials. |
| CVE-2026-130802 | Unknown | 2026-11-17 | Not applicable | No public exploit | The NFC authentication handshake relies on a fixed, static challenge instead of a unique, random value for every session. This allows an attacker to perform a "replay attack," successfully authenticating by simply sending the same pre-recorded response. |
| CVE-2026-130801 | Unknown | 2026-11-17 | Not applicable | No public exploit | The device's command parser does not require asymmetric cryptographic signatures to validate incoming APDU packets. This enables an attacker to inject forged, unauthorized commands to manipulate device features and configurations once the initial handshake is bypassed. |
| CVE-2026-130635 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC before 26.07.0 contains an uncontrolled recursion vulnerability in dasher_gather_deps() in src/filters/dasher.c that fails to detect cyclic stream dependency chains. Attackers can supply a crafted MPEG-2 TS file that MP4Box processes with -dash, exhausting the stack and crashing the process for denial of service. |
| CVE-2026-130634 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC before 26.07.0 contains a heap-based buffer overflow in gf_mpd_resolve_url() in src/media_tools/mpd.c that allows attackers to write past a heap buffer via crafted DASH manifests. Attackers can supply a crafted MPD whose segment template expands beyond the allocation through unchecked strcat() calls, crashing MP4Box and causing denial of service. |
| CVE-2026-130633 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC before 26.02.0 contains a use-after-free vulnerability in gf_filter_pid_set_args_internal() that leaves a stale pointer after gf_props_reset_single() frees a parsed PID property value. Attackers can supply a crafted filelist input processed by MP4Box with -add, causing gf_props_del_property() to access freed memory and crash the application. |
| CVE-2026-130632 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC before 26.02.0 contains an out-of-bounds read vulnerability in m2tsdmx_send_packet() in src/filters/dmx_m2ts.c caused by double-skipping the VC-1 start-code offset. Attackers can supply a crafted MPEG-2 TS VC-1 stream that underflows the remaining length, causing memcpy() to over-read and crash MP4Box on import. |
| CVE-2026-130631 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC before 26.07.0 contains an uninitialized pointer access vulnerability in GetESD() in src/isomedia/track.c that allows attackers to trigger invalid memory reads via crafted MP4 files. Attackers can supply an MP4 with an rvcc box having predefined_rvc_config set to 0 and no meta item index, causing strcmp() on an uninitialized mime_type pointer and crashing MP4Box -add. |
| CVE-2026-130630 | Medium | 2026-11-17 | Not applicable | No public exploit | GPAC 26.02.0 contains a NULL pointer dereference vulnerability in dasher_configure_pid() in src/filters/dasher.c that dereferences ds2->set without checking for NULL. Attackers can supply a crafted MPEG-2 TS file processed with MP4Box -dash to disconnect a PID and crash MP4Box, causing denial of service. |
| CVE-2026-130629 | Low | 2026-11-17 | Not applicable | No public exploit | react-native-webview 13.8.0 through 17.1.0 contains a code injection vulnerability that allows attackers to execute JavaScript by placing unescaped backticks or ${} sequences in injectedJavaScriptObject string values. Attackers who control values like profile fields or API responses can break out of the template literal to access the page DOM, non-HttpOnly cookies, and the ReactNativeWebView message bridge. |
| CVE-2026-130628 | Medium | 2026-11-17 | Not applicable | No public exploit | react-native-webview 13.7.0 through 17.1.0 on Windows contains an unrestricted URI scheme launch vulnerability in the WebView2 OnCoreWebView2NewWindowRequested handler, which passes requested URIs to LaunchUriAsync without scheme or user-initiation checks. Malicious web content can call window.open() or use target=_blank links with schemes like ms-settings: to launch Windows protocol handlers without the external-protocol confirmation prompt. |
| CVE-2026-130615 | High | 2026-11-17 | Not applicable | No public exploit | Flowise through 3.1.4 contains a server-side request forgery vulnerability that allows authenticated users to reach internal services by exploiting unpinned DNS validation in checkDenyList(). Attackers can configure a chatflow with Playwright or Puppeteer loaders using a DNS-rebinding domain so headless Chromium fetches internal or cloud metadata endpoints, returning responses as document content. |
| CVE-2026-130608 | High | 2026-11-17 | Not applicable | No public exploit | When using the admin area profile form to change ones profile details *except* the password (so, email or username), the password field in the database is overwritten with the plaintext password. Further login is not possible, so the error is noticeable, but the password is leaked to the database. |
| CVE-2026-130596 | Medium | 2026-11-17 | Not applicable | No public exploit | FusionPBX through 5.6.5 contains a path traversal vulnerability in app/fax/fax_emails.php that allows unauthenticated remote attackers to write files by using a crafted MIME attachment filename. Attackers can email the polled fax mailbox with a spoofed authorized From address and use ../ sequences in the filename to create or overwrite web-server-writable files with .pdf/.tif content. |
| CVE-2026-130595 | Medium | 2026-11-17 | Not applicable | No public exploit | SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL dangerous-function denylist because DS_SPECIFIC_DANGEROUS_FUNCTIONS uses 'postgresql' while lookups use the 'pg' type. Authenticated users can steer LLM-generated SQL past check_sql_read() using pg_read_file, pg_write_file, lo_import or lo_export to read or write files on the database host. |
| CVE-2026-130594 | Medium | 2026-11-17 | Not applicable | No public exploit | Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site scripting vulnerability that allows attackers to inject scripts by supplying unescaped ScalarConfig title values. Attackers controlling title metadata can close the title element with </title> and inject a script tag that executes in the documentation origin for API reference visitors. |
| CVE-2026-130593 | Medium | 2026-11-17 | Not applicable | No public exploit | Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site scripting vulnerability in get_scalar_api_reference() that embeds unescaped OpenAPI content inside an inline script element. Attackers can supply an OpenAPI document containing a </script><script> sequence in content or sources to execute scripts in the documentation origin for every user viewing the API reference. |
| CVE-2026-130591 | High | 2026-11-17 | Not applicable | No public exploit | 53AIHub before 0.5.5 contains a missing authentication vulnerability that allows unauthenticated attackers to read files by requesting /api/files/:file_id/preview and /api/file-version/:file_body_id without UserTokenAuth. Attackers can enumerate sequential numeric ids to read raw knowledge-base files and stored file versions belonging to any enterprise tenant. |
| CVE-2026-130590 | Medium | 2026-11-17 | Not applicable | No public exploit | react-native-webview 11.25.1 through 17.1.0 on Android contains a denial of service vulnerability that allows web content to crash the host application via malformed Content-Disposition headers. Attackers can serve a download whose filename* parameter has invalid percent-encoding, triggering an uncaught IllegalArgumentException in URLUtil.parseContentDisposition on the main thread to terminate the app. |
| CVE-2026-130589 | High | 2026-11-17 | Not applicable | No public exploit | Emitter through 3.1 contains a privilege escalation vulnerability that allows any channel key holder to forge a master key because channel keys use bare XOR Salsa20 encryption without a MAC or signature. Attackers can flip the permissions byte to the master value and present the forged key to the keygen service to mint keys with arbitrary permissions on every channel of the contract. |
| CVE-2026-130588 | High | 2026-11-17 | Not applicable | No public exploit | OpenFunction through 1.2.0 contains a NULL pointer dereference vulnerability in getServingRun that allows users permitted to create Serving resources to crash the operator by omitting the triggers section. Attackers can submit a Serving with nil Spec.Triggers to crash-loop the controller-manager, halting Function and Serving reconciliation cluster-wide until the object is deleted. |
| CVE-2026-130587 | Critical | 2026-11-17 | Not applicable | No public exploit | OpenFunction through 1.2.0 contains a privilege escalation vulnerability that allows namespace tenants to create privileged host-access pods by supplying unrestricted PodSpec templates in Function and Serving resources. Attackers with only Function or Serving create permissions can set privileged, hostNetwork, hostPID, or hostPath fields to mount the worker node's root filesystem and escalate to node access. |
| CVE-2026-130586 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | |
| CVE-2026-130585 | Unknown | 2026-11-17 | Withdrawn CVE | No public exploit | |
| CVE-2026-130584 | High | 2026-11-17 | Not applicable | No public exploit | Xibo CMS before 4.5.3 contains an insecure direct object reference vulnerability that allows authenticated users to access other DataSets' RSS feeds by pairing their own DataSet id with a foreign RSS id. Attackers with dataset.modify permission can read, edit, or delete feeds and steal PSKs, then use the unauthenticated /rss/{psk} endpoint to exfiltrate victim DataSet rows. |
| CVE-2026-130583 | Critical | 2026-11-17 | Not applicable | No public exploit | Rootways Authorize.net CIM Pro extension for Magento 2 before 4.1.5 contains an unauthenticated server-side request forgery vulnerability in the Apple Pay merchant validation controller. Attackers can supply file://, gopher://, or dict:// URLs in the validationUrl parameter to read app/etc/env.php credentials and encryption keys or reach internal services and cloud metadata endpoints. |
| CVE-2026-130387 | Medium | 2026-11-17 | Not applicable | No public exploit | Contiki-NG through 5.2 contains an out-of-bounds read vulnerability in coap_remove_observer_by_uri() that allows unauthenticated remote attackers to read past the supplied URI buffer. Attackers can send a CoAP GET Observe request with a Uri-Path shorter than an existing observer's URL, causing memcmp with strlen to read beyond the non-NUL-terminated buffer. |
| CVE-2026-130386 | High | 2026-11-17 | Not applicable | No public exploit | Contiki-NG through 5.2 contains an out-of-bounds access vulnerability in buffer_reclaim() and domain_set_free() in mpl.c that iterate the seed_set array one element past its end. Remote attackers can flood MPL multicast messages to fill the buffered message set, triggering out-of-bounds reads and writes of adjacent static memory that cause memory corruption or a crash. |
| CVE-2026-130385 | Low | 2026-11-17 | Not applicable | No public exploit | Weblate 2026.11 through 2026.11.2 contains a time-of-check time-of-use race condition in the GET /api/tasks/{pk}/ endpoint that exposes unredacted repository error messages. Authenticated project members lacking vcs.view permission can poll failing repository tasks to obtain RepositoryCommandError text revealing upstream repository URLs, filesystem paths, and host names. |
| CVE-2026-130384 | Medium | 2026-11-17 | Not applicable | No public exploit | Zammad before 7.2.3 contains a missing authorization vulnerability that allows authenticated customers to delete agents' shared ticket drafts by supplying a shared_draft_id. Attackers can create tickets via POST /api/v1/tickets or reply to accessible tickets referencing a draft id, destroying draft text prepared by agents. |
| CVE-2026-130383 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ before 4.1.12 and 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows authenticated editors to manipulate search index documents by supplying an arbitrary solutionId to the /admin/api/faq/update endpoint. On Elasticsearch or OpenSearch deployments, category-restricted editors can remove published FAQs from search, overwrite other FAQs' search documents, or plant entries that remain searchable after unpublishing. |
| CVE-2026-130382 | High | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an authentication bypass vulnerability in OtpLoginPlugin that allows attackers knowing the database password to skip TOTP verification by abusing the permanent-login cookie. Attackers can submit a login with a wrong OTP and permanent=1 to obtain a neo_permanent cookie, then replay it to gain full authenticated database access. |
| CVE-2026-130381 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass vulnerability that allows language-scoped editors to read other translations by checking FAQ_EDIT against the route language but loading the ?lang= UI-language row. Attackers can request the admin.faq.edit route with an authorized language and a different lang parameter to read drafts, private notes, author e-mails and revisions. |
| CVE-2026-130379 | Medium | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to bypass the privileged-port restriction by injecting separator characters or connection-string keywords into the login server field. Attackers can make pgsql, Mongo, Oracle and PDO drivers parse a different host and port, reaching internal services and leaking limited information through driver responses and errors. |
| CVE-2026-130378 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a filter injection vulnerability in its MongoDB driver that allows attackers to affect other documents by embedding ' AND ' or ') OR (' delimiters in a string _id or searched value. Attackers who can store a crafted document can cause a victim's delete or edit to match unintended documents, deleting the entire collection or modifying another document. |
| CVE-2026-130377 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in DELETE /admin/api/faq/delete that lets language-scoped FAQ_DELETE admins bypass their language scope. Attackers can submit a faqId with an in-scope faqLanguage lacking a translation to wipe shared ACL, tags, votes, comments, and attachments of other translations. |
| CVE-2026-130375 | High | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a remote code execution vulnerability that allows authenticated SQLite users to bypass the check_sqlite_name() extension guard using PDO_SQLite file: URI database names. Attackers can select the PDO driver with ext=pdo and submit names like file:/webroot/x.php?x=.db to create a .php file, then store PHP source as table data for code execution. |
| CVE-2026-130374 | High | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an sql injection vulnerability that allows remote attackers to inject SQL by supplying crafted IN and NOT IN search values that process_length() passes unescaped. Attackers can send a logged-in user a cross-site GET link using a backslash-escaped apostrophe to run blind SQL with that user's database rights on PostgreSQL, SQLite, MS SQL, Oracle, or MySQL in NO_BACKSLASH_ESCAPES mode. |
| CVE-2026-130373 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a stored HTML injection vulnerability that allows database users to inject markup by creating FULLTEXT indexes with crafted names. Attackers with CREATE, ALTER or INDEX rights can store markup rendered unescaped in the selection search form, enabling meta refresh redirects, content spoofing and form tampering against other users. |
| CVE-2026-130371 | Critical | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass vulnerability because the web installer ignores the legacy config/database.php during 3.x upgrades. Unauthenticated attackers can reinstall the site against an attacker-controlled database and create their own administrator account to take over the application. |
| CVE-2026-130370 | Low | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authentication vulnerability that allows attackers holding a hijacked session to enroll passkeys using only the session and webauthn CSRF token. Attackers can call /api/webauthn/prepare and /api/webauthn/register to replace the owner's passkeys, gaining persistent passwordless login that survives password changes and resets. |
| CVE-2026-130369 | Critical | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in multisite deployments that allows attackers to overwrite passkeys of accounts on other tenants via a shared PHP session store. Attackers can run WebAuthn prepare() for a login on one tenant, then replay the session against /api/webauthn/register on another tenant or the master to replace that user's passkeys and log in as admin. |
| CVE-2026-130367 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ through 4.1.12 and from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the admin FAQ copy and translate pages, which check only global FAQ_ADD or FAQ_TRANSLATE rights. Authenticated add-only or category-scoped editors can open any FAQ to read drafts, ACL-restricted records, private notes, and author e-mail addresses. |
| CVE-2026-130366 | Critical | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an authentication bypass vulnerability in the ClickHouse driver that allows remote attackers to log in to passwordless accounts without the configured defaultPasswordHash password. Attackers who know the name of a ClickHouse no_password account can submit any non-empty password, because connect() skips openPasswordless(), and obtain a session with that account's rights. |
| CVE-2026-130365 | Low | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha before 4.2.0-RC.2 contains a stored cross-site scripting vulnerability that allows FAQ_EDIT users to bypass SvgSanitizer using namespace-prefixed elements like <x:script>. Attackers can upload malicious SVGs through the admin image upload so script runs in the site origin on IIS, hijacking sessions of users like super-admins. |
| CVE-2026-130363 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that lets scoped editors view out-of-scope draft FAQs because the dashboard and admin search ignore category/language-scoped FAQ_EDIT rights. Authenticated editors can load the unpublished FAQs widget with the lang parameter or query /admin/api/faq/search to leak draft titles, ids, and confirm words in draft bodies. |
| CVE-2026-130362 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an account enumeration vulnerability that allows unauthenticated attackers to identify valid logins through differing POST /api/webauthn/prepare responses. Attackers can submit wordlists of usernames, reusing one unconsumed CSRF token without rate limiting, to discover administrator logins for password spraying and phishing. |
| CVE-2026-130361 | High | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a parameter injection vulnerability in its ClickHouse driver that allows attackers to inject ClickHouse HTTP query parameters through an unencoded db GET parameter. Attackers can lure a logged-in victim into opening a crafted GET link that injects a query parameter, bypassing the POST-only CSRF token. ClickHouse then executes attacker-chosen SQL under the victim's credentials to read, modify, or drop data. |
| CVE-2026-130359 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in SlugifyEditPlugin::getFieldInput() that embeds column names unescaped in an inline initSlugField() call. Attackers with DDL privileges can create a slug column whose name contains a single quote, injecting JavaScript that runs under the page's CSP nonce when victims open the table's edit form. |
| CVE-2026-130358 | Medium | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a missing authentication vulnerability in the ClaudeSqlPlugin, GeminiSqlPlugin, and OpenWebUiPlugin sendHeaders() handlers that run on the login page. Unauthenticated attackers can POST claude, gemini, or openwebui fields to relay arbitrary prompts using the operator's API key or bearer token, including to internal Open WebUI endpoints. |
| CVE-2026-130357 | High | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an improper authorization vulnerability in updateUserRights that lets USER_EDIT admins drop category restrictions on group rights. Attackers can re-save rights through the user update-rights API to convert category-restricted group rights into global direct rights, then edit, publish or delete FAQs in withheld categories. |
| CVE-2026-130355 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability in POST /admin/api/faq/import that lets FAQ_ADD users bypass the FAQ_PUBLISH right. Authenticated contributors can upload a CSV with column 8 set to true to publish unreviewed, optionally sticky FAQs such as phishing content. |
| CVE-2026-130354 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass vulnerability in POST /api/webauthn/prepare that creates accounts as active, bypassing manual activation and domain whitelisting. Anonymous attackers can obtain the freely issued CSRF token and register an activated account with an unverified email to access registered-user-only content and functions. |
| CVE-2026-130353 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability in its public FAQ REST API that exposes author names and e-mail addresses to unauthenticated callers. Attackers can query the faq and paginated faqs endpoints to bulk-harvest e-mails and de-anonymise users who opted out of GDPR author visibility. |
| CVE-2026-130351 | High | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the multisite Redis configuration store that is not tenant-scoped. As a result, tenant administrators can read and overwrite the master instance's effective configuration. Attackers can save configuration through /admin/api/configuration, optionally resetting storage.redisPrefix, to redirect master SMTP, set a known API token, or alter authentication settings. |
| CVE-2026-130350 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows delegated group or user admins to remove rights they do not hold by submitting empty rights lists. Attackers can send an empty rightIds or userRights array to group/permissions or user/update-rights to wipe all rights of more-privileged groups or administrators. |
| CVE-2026-130349 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an incorrect authorization vulnerability that allows category- or language-restricted editors to bypass scoped rights via public REST write endpoints. Attackers with a scoped right and the shared API token can use PUT faq/update, POST faq/create, and POST category to rewrite published FAQs and create root categories outside their scope. |
| CVE-2026-130347 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass in password reset, letting external-identity accounts receive local passwords. Attackers with mailbox access can request reset tokens for OIDC, Keycloak, Entra ID, LDAP, SSO, or WebAuthn accounts and log in locally, skipping IdP MFA and deprovisioning. |
| CVE-2026-130346 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an sql injection vulnerability in the ClickHouse driver because idf_escape() doubles backticks but does not escape backslashes in identifiers. Attackers can lure a logged-in user into opening a GET link with a column name ending in a backslash in columns, where, or order parameters, causing query text to be parsed as SQL. |
| CVE-2026-130345 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows authenticated frontend users to receive restricted FAQ titles by subscribing to Web Push notifications. When editors publish user/group-restricted FAQs, WebPushService::sendToAll() delivers the question, FAQ id, category, and slugified URL to every subscriber, bypassing the FAQ ACL. |
| CVE-2026-130343 | Medium | 2026-11-17 | Not applicable | No public exploit | phpMyFAQ 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authorization bypass vulnerability in the user/request-removal API endpoint that lets authenticated users file account removal requests as other users. The ownership check calls getUserById() with the attacker-supplied userId on the session user object, so it compares the input against the target's own record. Attackers who know a victim's login name and email can submit that userId, loginname, and email, sending administrators a spoofed Remove User Request email. This may lead an admin to delete the victim's account and data. |