Overview 426,307 matches · 17,138 in Waratek scope · 1,801 protected · 5,926 exploited · 1,781 CISA KEV · 31,212 public PoC · 4,384 EPSS ≥ 0.5
426,307matches
17,138in Waratek scope4.0%
1,801protected0.4%
5,926exploited1.4%
1,781CISA KEV0.4%
31,212public PoC7.3%
4,384EPSS ≥ 0.51.0%
Protected by Waratek
1,808
0.4%
Rule in development
7
0.0%
Mitigation candidate
409
0.1%
No exploit published
14,914
3.5%
Outside Waratek scope
4,846
1.1%
Not applicable
385,148
90.3%
Withdrawn CVE
19,175
4.5%
Critical
44,021
10.3%
High
165,694
38.9%
Medium
175,169
41.1%
Low
17,985
4.2%
None
79
0.0%
Unknown
23,359
5.5%
split by
peak 101,044 / year
19902
Not applicable2
High2
not blocked2
No public exploit2
199115
Not applicable15
High11
Medium4
not blocked15
Working exploit published2
No public exploit13
199214
Not applicable13
Withdrawn CVE1
High12
Low1
Unknown1
not blocked14
No public exploit14
199313
Not applicable13
High8
Medium3
Low2
not blocked13
No public exploit13
199426
Not applicable25
Withdrawn CVE1
High14
Medium10
Low1
Unknown1
not blocked26
Working exploit published6
No public exploit20
199525
Not applicable25
Critical1
High17
Medium6
Low1
not blocked25
Working exploit published5
No public exploit20
199675
No exploit published1
Not applicable73
Withdrawn CVE1
Critical1
High43
Medium21
Low9
Unknown1
not blocked75
Working exploit published18
Forecast only1
No public exploit56
1997253
Not applicable252
Withdrawn CVE1
Critical1
High143
Medium89
Low19
Unknown1
not blocked253
Exploited2
Working exploit published73
Forecast only2
No public exploit176
1998247
Not applicable246
Withdrawn CVE1
Critical1
High137
Medium85
Low23
Unknown1
not blocked247
Exploited1
Working exploit published50
No public exploit196
1999923
No exploit published2
Outside Waratek scope1
Not applicable891
Withdrawn CVE29
Critical3
High423
Medium357
Low111
Unknown29
not blocked923
Exploited2
Working exploit published282
No public exploit639
20001,020
Mitigation candidate6
No exploit published6
Outside Waratek scope2
Not applicable1,005
Withdrawn CVE1
Critical2
High454
Medium467
Low96
Unknown1
not blocked1,020
Exploited5
Working exploit published427
Forecast only1
No public exploit587
20011,679
Protected by Waratek1
Mitigation candidate2
No exploit published10
Outside Waratek scope14
Not applicable1,649
Withdrawn CVE3
Critical12
High776
Medium706
Low182
Unknown3
blocked by ARMR today1
not blocked1,678
Exploited14
Working exploit published480
Forecast only2
No public exploit1,183
20022,170
Protected by Waratek3
Mitigation candidate8
No exploit published26
Outside Waratek scope12
Not applicable2,107
Withdrawn CVE14
Critical10
High1,023
Medium980
Low143
Unknown14
blocked by ARMR today3
not blocked2,167
Exploited12
Working exploit published545
Forecast only9
No public exploit1,604
20031,548
Protected by Waratek2
Mitigation candidate7
No exploit published30
Outside Waratek scope6
Not applicable1,482
Withdrawn CVE21
Critical9
High674
Medium747
Low97
Unknown21
blocked by ARMR today2
not blocked1,546
Exploited10
Working exploit published499
Forecast only1
No public exploit1,038
20042,479
Protected by Waratek2
Mitigation candidate1
No exploit published24
Outside Waratek scope8
Not applicable2,416
Withdrawn CVE28
Critical10
High973
Medium1,265
Low203
Unknown28
blocked by ARMR today2
not blocked2,477
Exploited21
Working exploit published755
Forecast only1
No public exploit1,702
20055,010
Protected by Waratek3
Mitigation candidate4
No exploit published75
Outside Waratek scope17
Not applicable4,833
Withdrawn CVE78
Critical13
High2,048
Medium2,430
Low441
Unknown78
blocked by ARMR today3
not blocked5,007
Exploited22
Working exploit published1,341
Forecast only11
No public exploit3,636
20066,659
Protected by Waratek8
Mitigation candidate4
No exploit published121
Outside Waratek scope67
Not applicable6,408
Withdrawn CVE51
Critical12
High2,763
Medium3,324
Low509
Unknown51
blocked by ARMR today8
not blocked6,651
Exploited37
Working exploit published2,440
Proof of concept only1
Forecast only6
No public exploit4,175
20076,596
Protected by Waratek6
Mitigation candidate10
No exploit published134
Outside Waratek scope83
Not applicable6,283
Withdrawn CVE80
Critical21
High3,162
Medium3,101
Low232
Unknown80
blocked by ARMR today6
not blocked6,590
Exploited47
Working exploit published2,495
Proof of concept only5
Forecast only5
No public exploit4,044
20085,664
Protected by Waratek7
Mitigation candidate9
No exploit published120
Outside Waratek scope74
Not applicable5,422
Withdrawn CVE32
Critical19
High2,846
Medium2,582
Low185
Unknown32
blocked by ARMR today7
not blocked5,657
Exploited42
Working exploit published2,518
Proof of concept only4
Forecast only9
No public exploit3,091
20095,778
Protected by Waratek9
Mitigation candidate13
No exploit published181
Outside Waratek scope62
Not applicable5,467
Withdrawn CVE46
Critical15
High2,734
Medium2,786
Low197
Unknown46
blocked by ARMR today9
not blocked5,769
Exploited73
Working exploit published2,591
Proof of concept only2
Forecast only3
No public exploit3,109
20104,667
Protected by Waratek9
Mitigation candidate12
No exploit published162
Outside Waratek scope86
Not applicable4,370
Withdrawn CVE28
Critical28
High2,093
Medium2,241
Low277
Unknown28
blocked by ARMR today9
not blocked4,658
Exploited73
Working exploit published1,313
Proof of concept only1
Forecast only9
No public exploit3,271
20114,172
Protected by Waratek6
Mitigation candidate9
No exploit published178
Outside Waratek scope116
Not applicable3,841
Withdrawn CVE22
Critical5
High1,784
Medium2,101
Low260
Unknown22
blocked by ARMR today6
not blocked4,166
Exploited50
Working exploit published691
Proof of concept only5
Forecast only4
No public exploit3,422
20125,351
Protected by Waratek9
Mitigation candidate24
No exploit published278
Outside Waratek scope94
Not applicable4,883
Withdrawn CVE63
Critical21
High1,724
Medium3,035
Low508
Unknown63
blocked by ARMR today9
not blocked5,340
not established2
Exploited59
Working exploit published831
Proof of concept only7
Forecast only46
No public exploit4,408
20135,324
Protected by Waratek26
Mitigation candidate18
No exploit published305
Outside Waratek scope300
Not applicable4,538
Withdrawn CVE137
Critical23
High1,735
Medium2,914
Low515
Unknown137
blocked by ARMR today26
not blocked5,297
not established1
Exploited97
Working exploit published520
Proof of concept only3
Forecast only21
No public exploit4,683
20148,008
Protected by Waratek41
Mitigation candidate12
No exploit published282
Outside Waratek scope253
Not applicable7,340
Withdrawn CVE80
Critical20
High1,938
Medium5,314
Low656
Unknown80
blocked by ARMR today41
not blocked7,967
Exploited97
Working exploit published795
Proof of concept only13
Forecast only16
No public exploit7,087
20156,595
Protected by Waratek32
Mitigation candidate6
No exploit published285
Outside Waratek scope202
Not applicable5,969
Withdrawn CVE101
Critical51
High2,354
Medium3,501
Low588
Unknown101
blocked by ARMR today32
not blocked6,563
Exploited95
Working exploit published647
Proof of concept only16
Forecast only19
No public exploit5,818
20166,517
Protected by Waratek58
Mitigation candidate12
No exploit published465
Outside Waratek scope129
Not applicable5,785
Withdrawn CVE68
Critical887
High2,895
Medium2,446
Low221
Unknown68
blocked by ARMR today57
partly blocked1
not blocked6,458
not established1
Exploited103
Working exploit published429
Proof of concept only27
Forecast only32
No public exploit5,926
201718,113
Protected by Waratek104
Mitigation candidate14
No exploit published682
Outside Waratek scope245
Not applicable13,597
Withdrawn CVE3,471
Critical2,113
High6,608
Medium5,687
Low234
Unknown3,471
blocked by ARMR today102
partly blocked2
not blocked18,009
Exploited211
Working exploit published1,260
Proof of concept only52
Forecast only23
No public exploit16,567
201818,154
Protected by Waratek176
Mitigation candidate16
No exploit published697
Outside Waratek scope338
Not applicable15,283
Withdrawn CVE1,644
Critical2,616
High7,571
Medium6,163
Low160
Unknown1,644
blocked by ARMR today175
partly blocked1
not blocked17,978
Exploited236
Working exploit published1,069
Proof of concept only87
Forecast only33
No public exploit16,729
201918,938
Protected by Waratek123
Rule in development1
Mitigation candidate23
No exploit published756
Outside Waratek scope514
Not applicable15,888
Withdrawn CVE1,633
Critical2,657
High7,227
Medium7,117
Low304
Unknown1,633
blocked by ARMR today121
partly blocked2
not blocked18,814
not established1
Exploited327
Working exploit published784
Proof of concept only126
Forecast only52
No public exploit17,649
202019,222
Protected by Waratek154
Mitigation candidate34
No exploit published898
Outside Waratek scope503
Not applicable16,733
Withdrawn CVE900
Critical2,780
High7,782
Medium7,359
Low401
Unknown900
blocked by ARMR today154
not blocked19,068
Exploited343
Working exploit published603
Proof of concept only156
Forecast only66
No public exploit18,054
202121,950
Protected by Waratek124
Rule in development1
Mitigation candidate24
No exploit published649
Outside Waratek scope491
Not applicable18,860
Withdrawn CVE1,801
Critical2,850
High8,770
Medium8,137
Low392
Unknown1,801
blocked by ARMR today124
not blocked21,826
Exploited489
Working exploit published446
Proof of concept only217
Forecast only167
No public exploit20,631
202226,431
Protected by Waratek214
Rule in development1
Mitigation candidate20
No exploit published895
Outside Waratek scope401
Not applicable23,542
Withdrawn CVE1,358
Critical4,441
High10,337
Medium9,908
Low385
Unknown1,360
blocked by ARMR today214
not blocked26,217
Exploited478
Working exploit published566
Proof of concept only2,768
Forecast only97
No public exploit22,522
202330,949
Protected by Waratek161
Mitigation candidate40
No exploit published876
Outside Waratek scope263
Not applicable27,476
Withdrawn CVE2,133
Critical5,031
High11,637
Medium11,824
Low323
Unknown2,134
blocked by ARMR today161
not blocked30,786
not established2
Exploited566
Working exploit published557
Proof of concept only5,593
Forecast only110
No public exploit24,123
202440,704
Protected by Waratek106
Mitigation candidate29
No exploit published617
Outside Waratek scope237
Not applicable38,964
Withdrawn CVE751
Critical4,874
High15,332
Medium18,998
Low740
None1
Unknown759
blocked by ARMR today105
partly blocked1
not blocked40,598
Exploited743
Working exploit published405
Proof of concept only7,467
Forecast only83
No public exploit32,006
202549,972
Protected by Waratek103
Rule in development4
Mitigation candidate25
No exploit published723
Outside Waratek scope151
Not applicable47,144
Withdrawn CVE1,822
Critical4,490
High16,670
Medium23,043
Low3,040
None10
Unknown2,719
blocked by ARMR today103
not blocked49,867
not established2
Exploited725
Working exploit published594
Proof of concept only10,991
Forecast only17
No public exploit37,645
2026101,044
Protected by Waratek321
Mitigation candidate27
No exploit published5,436
Outside Waratek scope177
Not applicable92,308
Withdrawn CVE2,775
Critical11,004
High40,974
Medium36,418
Low6,529
None68
Unknown6,051
blocked by ARMR today321
not blocked100,722
not established1
Exploited946
Working exploit published454
Proof of concept only19,418
Forecast only5
No public exploit80,221
1990199319961999200220052008201120142017202020232026
| 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-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-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-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-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-130380 | Critical | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an authentication bypass vulnerability in the sqlsrv-based MS SQL driver that allows unauthenticated attackers to log in by submitting an empty username. Attackers can supply any non-empty password, triggering Windows integrated authentication that grants a full session with the web server identity's SQL Server privileges. |
| 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-130376 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in FileUploadPlugin that allows database users to store script-bearing SVG files by uploading unsanitized content. Attackers can upload a malicious SVG to a *_path field, executing script in the same-origin session of any administrator who opens the file link. |
| 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-130372 | Medium | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains an open redirect vulnerability that allows unauthenticated attackers to redirect authenticated users by injecting an external URL through the HTTP Referer header into the hidden referer field of the edit form. Attackers can lure users from a page with an unsafe-url referrer policy whose URL contains &select=, redirecting them to phishing sites after record edits. |
| 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-130368 | 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 an improper restriction of excessive authentication attempts vulnerability in PasswordChangeController::update() that bypasses the step-up throttle. Attackers holding a hijacked admin-area session can repeatedly guess faqpassword_old with a reusable CSRF token to learn the original password and take over the account. |
| 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-130364 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a reflected HTML injection vulnerability that allows remote attackers to inject markup by supplying crafted array keys in the where URL parameter. Attackers can trick logged-in users into opening a link whose unescaped keys land in select search form name attributes, enabling meta refresh redirects and content spoofing. |
| 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-130360 | Medium | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a reflected cross-site scripting vulnerability in EditorNeo that allows remote attackers to execute JavaScript by injecting quote characters into the request URI. Attackers can lure authenticated users to crafted edit links whose path breaks out of the CSP-nonced whisper script in editor/core/Admin.php, enabling session theft and database credential disclosure. |
| 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-130356 | 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 that lets category- or language-restricted editors rewrite visibility ACLs and tags of any FAQ. Attackers send faq/update requests with a target faqId and an untranslated lang to expose restricted FAQs, wipe tags, or overwrite orphaned FAQs. |
| 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-130352 | 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 that allows unauthenticated attackers to read editor-only Private Notes by querying the public FAQ list API. Attackers can page through GET /api/v4.0/faqs or /api/v3.1/faqs without credentials to retrieve the notes field of every anonymously readable FAQ, exposing internal remarks and ticket details. |
| 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-130348 | 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 a missing authorization vulnerability that exposes restricted and inactive category metadata to unauthenticated visitors. Attackers can enumerate category IDs via /category/{id}/{slug}.html or query /api/v4.0/categories to read names, descriptions, images and FAQ counts of restricted categories. |
| 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-130344 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in Admin::printTablePartitions() that allows authenticated users to inject HTML by placing markup in partition column names. Attackers with CREATE or ALTER privileges can create a partitioned table whose unescaped partition expression executes script when another user opens the table-structure page. |
| 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. |
| CVE-2026-130342 | Low | 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 improper reference counting flaw on multisite deployments, allowing editors to delete other instances' attachment files. Because linkedRecords() counts only the local faqattachment table, deleting an attachment with shared md5 content makes File::delete() unlink the shared blob, destroying another instance's files. |
| CVE-2026-130341 | 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 a stored cross-site scripting vulnerability that allows registered users to inject javascript: links via FAQ comments. When the comment editor is enabled, Utils::parseUrl() strips https:// from sanitized hrefs, turning an allowed https://javascript:443/ link into executable script that runs on the shared admin origin when clicked. |
| CVE-2026-130340 | 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 into another user's session via column type names rendered with innerHTML. Attackers can create a PostgreSQL type or table with markup in its name to render live elements in the help popup, enabling content spoofing and requests to attacker servers. |
| CVE-2026-130339 | 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 that allows authenticated low-privilege users to read unpublished FAQ titles via bookmark_action. Attackers can request FAQ detail pages with bookmark_action=add across sequential ids, then view /user/bookmarks to reveal draft and pending submission question text. |
| CVE-2026-130338 | Low | 2026-11-17 | Not applicable | No public exploit | AdminNeo before 5.9.1 contains a stored sql injection vulnerability in the MySQL driver that allows database users with table creation rights to inject SQL through unescaped geometry column names in unconvert_field(). Attackers can craft a column name containing an SQL expression that executes with another AdminNeo user's privileges when they edit a row, save it, or export the table. |
| CVE-2026-129321 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.8 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 planner-role permissions to set a future merge scheduling date on merge requests they authored, a capability restricted to developer-role permissions and above, due to insufficient permission enforcement on the merge scheduling field during merge request updates. |
| CVE-2026-129253 | 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 with developer-role permissions to bypass admin-configured AI tool governance controls in a governed namespace due to improper binding of authorization tokens to their intended workflow execution context. |
| CVE-2026-129252 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions 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 an unconfirmed email address to be automatically granted Group Owner-level membership during a group import operation, due to insufficient email verification enforcement in the member identity mapping process. |
| CVE-2026-128849 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to start a Duo Workflow session with elevated privileges beyond those declared by the foundational flow due to improper enforcement of privilege boundaries in certain client environments. |
| CVE-2026-126141 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.11 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 make requests to internal network services through repository import functionality due to insufficient validation of destination addresses. |
| CVE-2026-125920 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 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 cause a denial of service affecting Duo usage analytics due to improper input validation. |
| CVE-2026-125275 | High | 2026-11-17 | Not applicable | No public exploit | Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in device certificate verification in nerves-hub nerves_hub_web allows an unauthenticated remote attacker to cause a denial of service via a TLS client certificate whose CA is not registered. When a client certificate chains to a root in the device endpoint's trust store but no CA in the chain is registered in NervesHub, NervesHub.SSL.decide/2 refuses it with the reason :unknown_ca. Erlang/OTP ssl reads that reason as a missing trust anchor, looks for an alternative root, finds the same root and validates again without end. The handshake process queries the database on each pass and keeps running after the client disconnects, until the node restarts. The device endpoint trusts the public roots from CAStore unless DEVICE_SSL_CACERTFILE is set, so a client certificate from a public CA whose chain allows client authentication is sufficient. A chain that ends at a root outside the trust store is refused once. This issue affects nerves_hub: from 1.0.0 before 2.5.4. |
| CVE-2026-12487 | High | 2026-11-17 | Not applicable | No public exploit | An incorrect authorization vulnerability in the SNMP parameter of Zyxel EE5301-00 customized firmware version 5.63(ACLD.2)b3_D0 could allow an unauthenticated attacker to cause a denial-of-service (DoS) condition on an affected device. |
| CVE-2026-123142 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4 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 an MCP-scoped OAuth token to perform unauthorized issuable state changes on issues and merge requests, including approving and merging, due to incorrect authorization checks. |
| CVE-2026-122226 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 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 GitLab Duo features restricted by group-based access rules due to improper handling of failed updates to those rules. |
| CVE-2026-122045 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 16.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 authenticated user to configure GitLab Duo settings for groups without an eligible license due to missing authorization checks. |
| CVE-2026-121948 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab 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 to change the GitLab Duo Code Review consent setting of a parent group due to incorrect authorization checks. |
| CVE-2026-121684 | High | 2026-11-17 | Not applicable | No public exploit | The Soledad theme for WordPress is vulnerable to unauthenticated Remote Code Execution in versions up to, and including, 8.7.7 The public penci_more_post_ajax AJAX action feeds infeedads[ads_code] (base64+urldecoded) to penci_safe_shortcode(), whose allowlist regex inspects only the hyphen-truncated outer shortcode name (e.g. 'adinserter') and never the nested [elementor-element k=.. data=..] tag, so do_shortcode() renders an attacker-chosen Elementor element. The rendered penci-featured-sliders widget passes its unsanitized 'style' setting to include dirname(__FILE__)."/{$style}.php", a path-traversal local file inclusion. |
| CVE-2026-121533 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.8 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 restricted job artifact data due to missing authorization checks. |
| CVE-2026-120387 | Critical | 2026-11-17 | Not applicable | No public exploit | An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an unauthenticated remote attacker to bypass authentication by submitting an unsigned JWT with the algorithm set to “none”. The shared JWT validation component accepts the token without verifying a cryptographic signature, allowing the attacker to impersonate another user and access protected functionality with that user's privileges. |
| CVE-2026-118961 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 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 commit comments from a private source fork through a public project's merge request discussions due to missing authorization checks. |
| CVE-2026-11768 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.4 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 private CI/CD job artifacts belonging to other projects through GitLab Pages due to improper validation of file paths. |
| CVE-2026-115736 | 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 view unredacted secret values from secret detection findings they had access to through GitLab Duo Agent Platform due to improper authorization checks. |
| CVE-2026-115428 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.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 a valid agent token to cause a denial of service in the GitLab agent server (KAS) due to improper input validation. |
| CVE-2026-115219 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab 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 to enable Amazon Q automatic code reviews on a project despite an administrator lock due to improper enforcement of instance-level settings. |
| CVE-2026-115218 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.8 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 NuGet package metadata that should not have been accessible due to missing authorization checks. |
| CVE-2026-112203 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 18.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 individual controlling an upstream repository to alter cached Maven packages from other repositories in the same virtual registry due to improper response validation. |
| CVE-2026-111973 | Unknown | 2026-11-17 | Not applicable | No public exploit | The RSS Feed Retriever WordPress plugin through 1.6.10 does not validate a user-supplied URL before fetching it server-side with a bundled HTTP library that lacks WordPress's private-network protections, allowing unauthenticated users to make the site retrieve arbitrary internal or external resources and read the response. |
| CVE-2026-111747 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 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 hide changes from reviewers in merge request diffs due to improper handling of file names. |
| CVE-2026-110990 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1.7 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed sensitive credential values submitted in GraphQL requests to be written to logs in plaintext due to incomplete filtering of sensitive data. |
| CVE-2026-110750 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.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 to read Git LFS objects from projects restricted by External Authorization due to missing authorization checks. |
| CVE-2026-108155 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.12 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 Git LFS objects from restricted projects due to incorrect authorization checks. |
| CVE-2026-108154 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.0 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 import Git repositories into projects despite administrator restrictions on import sources due to missing authorization checks. |
| CVE-2026-108153 | High | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.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 execute arbitrary JavaScript in the browser of users viewing Error Tracking pages due to improper sanitization of user input. |
| CVE-2026-108150 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.12 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 private CI/CD template files from projects they did not have access to due to missing authorization checks. |
| CVE-2026-107904 | Unknown | 2026-11-17 | Not applicable | No public exploit | Joomla Extension - valorapps.com - Unauthenticated Remote Code Execution in Easy File Uploader < 2.9.7 - An unauthenticated remote attacker can upload a PHP-executable file to the Joomla web root with a single multipart POST request, requiring no credentials and no CSRF token. |
| CVE-2026-107902 | High | 2026-11-17 | Not applicable | No public exploit | TELLUS and TELLUS Lite provided by FUJI ELECTRIC CO., LTD. contain a use after free vulnerability. Opening a specially crafted V9 file may lead to information exposure or arbitrary code execution on the affected product. |
| CVE-2026-107901 | Medium | 2026-11-17 | Not applicable | No public exploit | TELLUS and TELLUS Lite provided by FUJI ELECTRIC CO., LTD. contain an out-of-bounds read vulnerability. Opening a specially crafted V9 file may lead to information exposure or arbitrary code execution on the affected product. |
| CVE-2026-105739 | High | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.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 to execute arbitrary JavaScript in the browser of users viewing a wiki page due to improper sanitization of user input. |
| CVE-2026-104934 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 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 files from a project's private repository due to missing authorization checks in snippets. |
| CVE-2026-104902 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 17.7 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 GitLab Duo seat assignments and usage data from other groups due to improper authorization checks. |
| CVE-2026-104717 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 13.4 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 view iteration details from private groups they did not have access to due to missing authorization checks. |
| CVE-2026-102907 | Medium | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.0 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 create issues with locked discussions despite lacking the required permissions due to improper authorization checks. |
| CVE-2026-101358 | Low | 2026-11-17 | Not applicable | No public exploit | GitLab has remediated an issue in GitLab EE affecting all versions from 17.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 authenticated user to read CI/CD variable metadata from projects they did not have access to due to improper authorization in pipeline execution policies. |
| CVE-2026-99311 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: udf: fix return value for non-recorded-allocated extents in udf_map_block() When someone creates a corrupted UDF filesystem where symlink contains other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash like: Oops: general protection fault KASAN: maybe wild-memory-access RIP: 0010:page_get_link (fs/namei.c:6503) Call Trace: vfs_readlink (fs/namei.c:6419) do_readlinkat (fs/stat.c:583) __x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602) This is because in this case udf_map_block() fails to convert return value of inode_bmap() from 1 to 0. Returned '1' propagates through udf_bread() all the way up to __page_get_link() where it ends up being treated as a folio pointer with obvious results. Move the reset to 0 line outside the if, so udf_map_block() returns either 0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED. |
| CVE-2026-99310 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: nfsd: hold cl_lock in client_has_openowners() client_has_openowners() walks clp->cl_openowners and reads so_stateids without clp->cl_lock. nfs4_put_stateowner() unhashes that openowner under cl_lock and then frees it, so a concurrent EXCHANGE_ID with mismatched creds can use-after-free the nfs4_openowner. BUG: KASAN: slab-use-after-free in client_has_state+0x10a/0x140 fs/nfsd/nfs4state.c:3718 client_has_openowners() nfsd4_exchange_id nfsd4_proc_compound nfsd_dispatch svc_process Take clp->cl_lock while client_has_openowners() walks the openowner list. |
| CVE-2026-99309 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix overflow in dacloffset bounds check in build_sec_desc() When the large dacl_offset is provided, dacl_offset + sizeof(struct smb_acl) overflows on 32-bit builds and the check is passed, Which makes le16_to_cpu(ppdacl_ptr->size) read out-of-bounds. This only happens for dacl_offset in range [0xFFFFFFF8, 0xFFFFFFFF]. So the oob read is max 8 bytes preceding the allocated ppntsd. unsigned int dacl_offset = le32_to_cpu(ppntsd->dacloffset); int ppdacl_size, ntacl_size = ppntsd_size - dacl_offset; if (!dacl_offset || (dacl_offset + sizeof(struct smb_acl) > ppntsd_size)) goto out; Commit beff0bc9d69b ("ksmbd: fix overflow in dacloffset bounds check") fixes similar checks in other functions. But leaves this one out, because it is only valid for 32-bit builds. Reproduced on 32-bit ARM with KASAN, by a client sending SMB2 SET_INFO(SEC) with dacloffset=0xfffffff8, then QUERY_INFO(SEC) on the same file: BUG: KASAN: slab-out-of-bounds in build_sec_desc (fs/smb/server/smbacl.c:1105) Read of size 2 at addr c2a273fa by task kworker/1:1/35 CPU: 1 UID: 0 PID: 35 Comm: kworker/1:1 Not tainted 7.3.0-rc2+ #5 Workqueue: ksmbd-io handle_ksmbd_work Call trace: kasan_check_range from build_sec_desc (fs/smb/server/smbacl.c:1105) build_sec_desc from smb2_query_info (fs/smb/server/smb2pdu.c:7676) smb2_query_info from handle_ksmbd_work (fs/smb/server/server.c:160) handle_ksmbd_work from process_one_work (kernel/workqueue.c:3401) process_one_work from worker_thread (kernel/workqueue.c:3473) worker_thread from kthread (kernel/kthread.c:436) Add overflow check. |
| CVE-2026-99308 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix bounce buffer overflow High-speed devices with out of spec 1024 byte bulk endpoints exist and are allowed by USB core, but xhci-hcd always sets packet size to 512. The exact nature of these devices isn't documented, commit fb5ee84ea72c ("USB: Accept bulk endpoints with 1024-byte maxpacket") only states that they "don't work with xHCI host controllers", whatever it means. But somebody (or a malicious device) can try, and then the driver will allocate a 512 byte bounce buffer for this endpoint and may write up to 1024 bytes into it if particular scatter-gather URBs are used, because xhci_align_td() obtains packet size from the descriptor. Fix this. As a side effect, TRBs will be aligned to the packet size chosen by the driver on all endpoints of all speeds. Alignment serves the xHC, not device, so this is fine. Only out of spec devices are affected anyway. |
| CVE-2026-99307 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ceph: require the dentry lease record to cover struct ceph_mds_reply_lease parse_reply_info_lease() reads a 32-bit struct_len off the wire and only checks that many bytes are present, without requiring struct_len to cover sizeof(struct ceph_mds_reply_lease) (10 bytes). A malicious MDS can declare a shorter record and still get the pointer published: the following *p += sizeof(**lease) overshoot is undone by *p = lend, so nothing downstream rejects the reply. ceph_fill_trace() -> update_dentry_lease() then reads 10 bytes through that pointer on any lookup on a mounted CephFS, running past the end of the message front. Require the record to cover the structure, matching the sibling parse_reply_info_dir(). A conforming MDS always encodes the full 10 bytes. BUG: KASAN: slab-out-of-bounds in __update_dentry_lease.constprop.0 (fs/ceph/inode.c:1459) Read of size 4 at addr ffff888026c63d65 by task kworker/0:3/2366 Workqueue: ceph-msgr ceph_con_workfn Call Trace: __update_dentry_lease.constprop.0 (fs/ceph/inode.c:1459) ceph_fill_trace (fs/ceph/inode.c:1474 fs/ceph/inode.c:1823) mds_dispatch (fs/ceph/mds_client.c:4229 fs/ceph/mds_client.c:7225) ceph_con_process_message (net/ceph/messenger.c:1424) ceph_con_v1_try_read (net/ceph/messenger_v1.c:1430) ceph_con_workfn (net/ceph/messenger.c:1576) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) The buggy address is located 357 bytes inside of allocated 360-byte region [ffff888026c63c00, ffff888026c63d68) |
| CVE-2026-99306 | Unknown | 2026-11-16 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ceph: reject mdsmaps that claim more than CEPH_MAX_MDS ranks check_new_map() sizes its export-target bitmap from CEPH_MAX_MDS but walks it with newmap->possible_max_rank, which comes straight off the wire: ceph_mdsmap_decode() sets it to max(m_num_active_mds, m_max_mds), then overwrites it with the size of the "in" set. Neither is bounded by CEPH_MAX_MDS, only by m_info allocating, so a monitor announcing more ranks than the bitmap holds makes test_bit() read past the end of targets[]. The clear_bit() loop above indexes the same bitmap, though it is additionally bounded by mdsc->max_sessions. The map arrives on the monitor connection, which is unauthenticated in legacy msgr mode. CEPH_MAX_MDS is a protocol constant from src/mds/mdstypes.h, and the reserved inode ranges in super.h are laid out one rank apart over that span, so a map claiming more ranks is corrupt. Reject it where the rank space is established rather than letting the count reach check_new_map(). BUG: KASAN: stack-out-of-bounds in check_new_map (fs/ceph/mds_client.c:5968) Read of size 8 at addr ffffc90000ac7798 by task kworker/1:2/127 Workqueue: ceph-msgr ceph_con_workfn Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) kasan_check_range (mm/kasan/generic.c:186 mm/kasan/generic.c:200) check_new_map (fs/ceph/mds_client.c:5968) ceph_mdsc_handle_mdsmap (fs/ceph/mds_client.c:7060) extra_mon_dispatch (fs/ceph/super.c:802) mon_dispatch (net/ceph/mon_client.c:1483) ceph_con_process_message (net/ceph/messenger.c:1424) ceph_con_v1_try_read (net/ceph/messenger_v1.c:1430) ceph_con_workfn (net/ceph/messenger.c:1576) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) </TASK> The buggy address belongs to stack of task kworker/1:2/127 and is located at offset 288 in frame: check_new_map (fs/ceph/mds_client.c:5846) This frame has 1 object: [32, 288) 'targets' |