Overview 430,468 matches · 18,093 in Waratek scope · 1,809 protected · 6,062 exploited · 1,790 CISA KEV · 31,274 public PoC · 4,401 EPSS ≥ 0.5
430,468matches
18,093in Waratek scope4.2%
1,809protected0.4%
6,062exploited1.4%
1,790CISA KEV0.4%
31,274public PoC7.3%
4,401EPSS ≥ 0.51.0%
Protected by Waratek
1,824
0.4%
Rule in development
7
0.0%
Mitigation candidate
461
0.1%
No exploit published
15,801
3.7%
Outside Waratek scope
3,538
0.8%
Not applicable
389,640
90.5%
Withdrawn CVE
19,197
4.5%
Critical
44,390
10.3%
High
167,184
38.8%
Medium
176,939
41.1%
Low
18,246
4.2%
None
79
0.0%
Unknown
23,630
5.5%
split by
peak 105,216 / year
19916
Not applicable6
High4
Medium2
not blocked6
No public exploit6
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 candidate7
No exploit published7
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 candidate4
No exploit published11
Outside Waratek scope10
Not applicable1,650
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 published28
Outside Waratek scope4
Not applicable2,113
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 candidate8
No exploit published31
Outside Waratek scope4
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 Waratek3
Mitigation candidate1
No exploit published25
Outside Waratek scope5
Not applicable2,417
Withdrawn CVE28
Critical10
High973
Medium1,265
Low203
Unknown28
blocked by ARMR today3
not blocked2,476
Exploited21
Working exploit published755
Forecast only1
No public exploit1,702
20055,010
Protected by Waratek3
Mitigation candidate5
No exploit published76
Outside Waratek scope15
Not applicable4,833
Withdrawn CVE78
Critical13
High2,048
Medium2,430
Low441
Unknown78
blocked by ARMR today3
not blocked5,007
Exploited23
Working exploit published1,340
Forecast only11
No public exploit3,636
20066,659
Protected by Waratek8
Mitigation candidate5
No exploit published127
Outside Waratek scope54
Not applicable6,414
Withdrawn CVE51
Critical12
High2,763
Medium3,324
Low509
Unknown51
blocked by ARMR today8
not blocked6,651
Exploited39
Working exploit published2,438
Proof of concept only1
Forecast only6
No public exploit4,175
20076,596
Protected by Waratek7
Mitigation candidate13
No exploit published146
Outside Waratek scope66
Not applicable6,284
Withdrawn CVE80
Critical21
High3,162
Medium3,101
Low232
Unknown80
blocked by ARMR today7
not blocked6,589
Exploited47
Working exploit published2,495
Proof of concept only5
Forecast only5
No public exploit4,044
20085,664
Protected by Waratek7
Mitigation candidate11
No exploit published134
Outside Waratek scope51
Not applicable5,429
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 candidate16
No exploit published195
Outside Waratek scope45
Not applicable5,467
Withdrawn CVE46
Critical15
High2,734
Medium2,786
Low197
Unknown46
blocked by ARMR today9
not blocked5,769
Exploited74
Working exploit published2,590
Proof of concept only2
Forecast only3
No public exploit3,109
20104,667
Protected by Waratek9
Mitigation candidate14
No exploit published168
Outside Waratek scope74
Not applicable4,374
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 candidate13
No exploit published205
Outside Waratek scope83
Not applicable3,843
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 candidate26
No exploit published291
Outside Waratek scope76
Not applicable4,886
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 candidate19
No exploit published318
Outside Waratek scope284
Not applicable4,540
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 candidate13
No exploit published292
Outside Waratek scope233
Not applicable7,349
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 Waratek33
Mitigation candidate7
No exploit published308
Outside Waratek scope171
Not applicable5,975
Withdrawn CVE101
Critical51
High2,354
Medium3,501
Low588
Unknown101
blocked by ARMR today33
not blocked6,562
Exploited96
Working exploit published647
Proof of concept only16
Forecast only19
No public exploit5,817
20166,517
Protected by Waratek61
Mitigation candidate10
No exploit published479
Outside Waratek scope108
Not applicable5,791
Withdrawn CVE68
Critical887
High2,895
Medium2,446
Low221
Unknown68
blocked by ARMR today59
partly blocked2
not blocked6,455
not established1
Exploited103
Working exploit published429
Proof of concept only27
Forecast only32
No public exploit5,926
201718,113
Protected by Waratek108
Mitigation candidate15
No exploit published701
Outside Waratek scope212
Not applicable13,606
Withdrawn CVE3,471
Critical2,113
High6,608
Medium5,687
Low234
Unknown3,471
blocked by ARMR today104
partly blocked4
not blocked18,005
Exploited212
Working exploit published1,259
Proof of concept only52
Forecast only23
No public exploit16,567
201818,154
Protected by Waratek183
Mitigation candidate23
No exploit published724
Outside Waratek scope205
Not applicable15,375
Withdrawn CVE1,644
Critical2,616
High7,571
Medium6,163
Low160
Unknown1,644
blocked by ARMR today182
partly blocked1
not blocked17,971
Exploited236
Working exploit published1,069
Proof of concept only87
Forecast only34
No public exploit16,728
201918,938
Protected by Waratek123
Rule in development1
Mitigation candidate32
No exploit published797
Outside Waratek scope262
Not applicable16,090
Withdrawn CVE1,633
Critical2,657
High7,227
Medium7,117
Low304
Unknown1,633
blocked by ARMR today121
partly blocked2
not blocked18,813
not established2
Exploited332
Working exploit published782
Proof of concept only126
Forecast only51
No public exploit17,647
202019,222
Protected by Waratek157
Mitigation candidate38
No exploit published943
Outside Waratek scope263
Not applicable16,921
Withdrawn CVE900
Critical2,780
High7,782
Medium7,359
Low401
Unknown900
blocked by ARMR today157
not blocked19,065
Exploited345
Working exploit published602
Proof of concept only155
Forecast only66
No public exploit18,054
202121,950
Protected by Waratek124
Rule in development1
Mitigation candidate28
No exploit published669
Outside Waratek scope331
Not applicable18,996
Withdrawn CVE1,801
Critical2,850
High8,770
Medium8,137
Low392
Unknown1,801
blocked by ARMR today124
not blocked21,826
Exploited491
Working exploit published446
Proof of concept only217
Forecast only166
No public exploit20,630
202226,431
Protected by Waratek215
Rule in development1
Mitigation candidate20
No exploit published901
Outside Waratek scope269
Not applicable23,667
Withdrawn CVE1,358
Critical4,441
High10,337
Medium9,908
Low385
Unknown1,360
blocked by ARMR today215
not blocked26,216
Exploited465
Working exploit published566
Proof of concept only2,769
Forecast only97
No public exploit22,534
202330,949
Protected by Waratek161
Mitigation candidate40
No exploit published882
Outside Waratek scope205
Not applicable27,528
Withdrawn CVE2,133
Critical5,031
High11,637
Medium11,824
Low323
Unknown2,134
blocked by ARMR today161
not blocked30,786
not established2
Exploited565
Working exploit published553
Proof of concept only5,591
Forecast only110
No public exploit24,130
202440,704
Protected by Waratek108
Mitigation candidate28
No exploit published619
Outside Waratek scope187
Not applicable39,011
Withdrawn CVE751
Critical4,874
High15,332
Medium18,998
Low740
None1
Unknown759
blocked by ARMR today106
partly blocked2
not blocked40,596
Exploited750
Working exploit published402
Proof of concept only7,465
Forecast only83
No public exploit32,004
202549,972
Protected by Waratek103
Rule in development4
Mitigation candidate25
No exploit published730
Outside Waratek scope140
Not applicable47,148
Withdrawn CVE1,822
Critical4,490
High16,670
Medium23,043
Low3,040
None10
Unknown2,719
blocked by ARMR today103
not blocked49,867
not established2
Exploited748
Working exploit published593
Proof of concept only10,978
Forecast only17
No public exploit37,636
2026105,216
Protected by Waratek314
Mitigation candidate32
No exploit published5,991
Outside Waratek scope180
Not applicable95,902
Withdrawn CVE2,797
Critical11,373
High42,473
Medium38,190
Low6,790
None68
Unknown6,322
blocked by ARMR today310
partly blocked4
not blocked104,901
not established1
Exploited1,051
Working exploit published479
Proof of concept only19,833
Forecast only6
No public exploit83,847
199319961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-134390 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in the make_merge_log endpoint that allows authenticated users to read POS Invoice data. Attackers can supply POS Invoice names outside their permitted scope to retrieve each invoice's customer, posting date, and grand total. |
| CVE-2026-134389 | High | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 6.18.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in Payment Requests that lets authenticated Accounts User role holders read source documents they lack permission to access. Attackers can create a Payment Request through the generic record interface that references another company's document, then email its loaded content to an address they choose. |
| CVE-2026-134388 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 14.0.0 before 15.124.0 and 16.x before 16.52.0 contains a stored cross-site scripting vulnerability in the CRM module because notes on Leads and Opportunities are saved without passing through the HTML sanitiser. Authenticated users with the Sales User role can save a note containing a crafted payload that executes in another user's session when they open the record, acting with that user's permissions. |
| CVE-2026-134387 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 12.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module dashboard chart source that returns account balance history without checking chart or account permissions. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming any account to read general ledger balance history of any company. |
| CVE-2026-134386 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 15.111.0 before 15.121.4 and 16.22.0 before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns item rows of a caller-named inter-company invoice or order and accepts a caller-supplied document type without checking read permission. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming another company's document to read Sales Invoice, Purchase Invoice and order items. |
| CVE-2026-134385 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 6.3.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint used to choose a Tax Rule, which returns party address details without permission checks. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming arbitrary customers, suppliers, or Addresses to obtain their city, state, postal code, and country. |
| CVE-2026-134384 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 13.0.0 before 15.124.2 and 16.x before 16.53.0 contains a missing authorization vulnerability in a Stock module endpoint that returns item cost data without checking the caller's permissions on the item, company, or warehouse. Authenticated attackers, including portal users or users restricted to other warehouses, can send crafted requests naming out-of-scope items, companies, or warehouses to obtain valuation rates and average purchase costs. |
| CVE-2026-134383 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 14.47.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in the Accounts module where a method on accounting vouchers creates and submits Repost Accounting Ledger documents with permission checks skipped. Authenticated users with read access to a Sales Invoice, Purchase Invoice, Payment Entry, Journal Entry, or Purchase Receipt can call it to delete and repost that voucher's General Ledger entries, an action restricted to System Managers. |
| CVE-2026-134382 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in a Selling module endpoint that checks only document-type write permission, not permission on each Sales Order, when closing or reopening Sales Orders. Authenticated users restricted by User Permissions can send crafted requests naming another company's Sales Order to close or reopen it outside their restriction. |
| CVE-2026-134381 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 5.0.0 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in the Buying module: the endpoint that closes and reopens Purchase Orders checks only document-type write permission, not per-document User Permissions. Authenticated users with Purchase Order write access can send crafted requests naming another company's Purchase Order to change its status. |
| CVE-2026-134379 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 8.2.5 before 15.121.4 and 16.x before 16.36.0 contains an incorrect authorization vulnerability in Manufacturing module endpoints that check only document-type write access, not permission on each Work Order. Authenticated users restricted by User Permissions can send crafted requests naming another company's Work Order to stop, resume or close it. |
| CVE-2026-134378 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 12.7.0 before 15.124.0 and 16.x before 16.52.0 stores imported Italian supplier e-invoices as public files in the Regional module, which the server returns without authentication. Unauthenticated attackers can request predictable file URLs built from the supplier's VAT number and invoice sequence to read supplier names, VAT numbers, bank account details and line items. |
| CVE-2026-134377 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 7.1.0 before 15.121.0 and 16.x before 16.34.0 contains a missing authorization vulnerability in Projects module endpoints that return Timesheet data without restricting results to records the caller may read. Any authenticated user, including one with no assigned roles, can send crafted requests to read organisation-wide Timesheet work and billing details. |
| CVE-2026-134376 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 11.0.0-beta before 15.122.0 and 16.x before 16.34.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns the subscription plans linked to a caller-named invoice without checking read permission on that invoice. Authenticated attackers can send crafted requests naming invoices outside their permitted scope to learn whether they belong to subscriptions and read the billed plans. |
| CVE-2026-134375 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 13.0.0 before 15.124.0 and 16.x before 16.52.0 contains an incorrect authorization vulnerability in an Accounts module endpoint that returns Payment Entries for a readable bank record without checking read permission on each Payment Entry. Authenticated users with an Accounts role can request a readable record to obtain metadata of Payment Entries excluded by their user permissions, such as Cost Center restrictions. |
| CVE-2026-134374 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 15.0.0 before 15.124.0 and 16.x before 16.52.0 contains a missing authorization vulnerability in Assets module endpoints that return a depreciation schedule for a caller-supplied asset without checking read permission on that asset. Authenticated users can name another company's asset to disclose its purchase value, value after depreciation, and depreciation entries. |
| CVE-2026-134373 | Medium | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 14.0.0 before 15.121.0 and 16.x before 16.34.0 contains a missing authorization vulnerability in a Utilities module endpoint that lets any authenticated user retry failed bulk transactions without a role check. Attackers, including portal users with no roles, can send crafted requests for a chosen date to mark site-wide failed bulk transactions as retried, removing them from the normal recovery path, and add background job load. |
| CVE-2026-134372 | High | 2026-11-21 | Not applicable | No public exploit | Frappe ERPNext 4.3.0 before 15.121.6 and 16.x before 16.37.0 contains an SQL injection vulnerability in an endpoint of the Selling and Buying modules, where a request value validated early can be overridden by caller-supplied data that reaches a database query unvalidated. Any authenticated user, including a portal user with no roles, can send crafted requests to extract sensitive data, including active session data, and take over other accounts such as administrators. |
| CVE-2026-134371 | High | 2026-11-21 | Not applicable | No public exploit | Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get_contact_number API that lets attackers read any Contact's phone numbers without permission checks. Attackers can call the endpoint, which uses an uncorrelated EXISTS subquery, to retrieve mobile_no and phone values of arbitrary Contact records, exposing PII. |
| CVE-2026-134370 | High | 2026-11-21 | Not applicable | No public exploit | Frappe Framework before 15.120.1 and 16.x before 16.33.1 contains a path traversal vulnerability in file attachment handling that permits arbitrary file read. Authenticated attackers holding a single ordinary role without write permissions can abuse attachment handling to read server files outside the application boundary. |
| CVE-2026-134367 | High | 2026-11-21 | Not applicable | No public exploit | pypdf 2.4.2 before 7.0.0 contains a resource exhaustion vulnerability in its handling of XFA forms that allows attackers to cause excessive memory consumption. Attackers can supply a crafted PDF containing XFA forms with many small fields so that loading the forms consumes large amounts of memory, causing a denial of service. |
| CVE-2026-134366 | High | 2026-11-21 | Not applicable | No public exploit | pypdf before 7.0.0 contains a resource exhaustion vulnerability that allows attackers to cause large memory usage by supplying crafted PDF cross-reference streams. Attackers can craft a PDF whose cross-reference stream offsets all point to one large object, exhausting memory in applications parsing the file. |
| CVE-2026-134364 | High | 2026-11-21 | Not applicable | No public exploit | pypdf 3.7.1 before 7.0.0 contains an information disclosure vulnerability that allows attackers to guess placeholders in encrypted templated documents by analyzing file identifiers. Attackers with a document sharing the same template and access to other documents' file identifiers can recover placeholder contents from encrypted PDFs. |
| CVE-2026-134363 | Low | 2026-11-21 | Not applicable | No public exploit | Coder 2.32.0 before 2.34.17, 2.35.0 before 2.36.12, 2.37.0 before 2.37.9, and 2.38.0 before 2.38.5 contain a symlink-following flaw in the Coder Agents read_skill_file tool, which validates skill file paths lexically but follows symlinks outside the skill directory. Attackers who place a malicious skill containing a symlinked supporting file in a victim's workspace can leak other workspace files into the model context and chat history when the victim runs a chat using that skill. |
| CVE-2026-134362 | Low | 2026-11-21 | Not applicable | No public exploit | Coder 2.6.0 before 2.29.26, 2.30.0 before 2.34.18, 2.35.0 before 2.37.10, and 2.38.0 before 2.38.6 contains a cross-site request forgery vulnerability because CSRF exemption patterns in coderd/httpmw/csrf.go are matched as unanchored regular expressions, letting affected API routes skip CSRF token and same-origin checks. Attackers controlling a page same-site with the deployment can make signed-in users' browsers send forged POST requests that recreate dev containers or add users whose names contain derp to organizations. |
| CVE-2026-134361 | High | 2026-11-21 | Not applicable | No public exploit | Coder 2.6.0 before 2.29.21, 2.30.0 before 2.34.10, 2.35.0 before 2.35.8, 2.36.0 before 2.36.5, and 2.37.0 before 2.37.1 contains a denial of service vulnerability in the workspace agent dRPC API, whose handlers dereference unset request sub-messages and unconfigured Tailnet providers without recovering from panics. Attackers holding a workspace agent token can send UpdateLifecycle, UpdateStartup, or BatchUpdateMetadata messages lacking sub-messages, or call RefreshResumeToken or WorkspaceUpdates, to repeatedly crash coderd. |
| CVE-2026-134360 | High | 2026-11-21 | Not applicable | No public exploit | Heym before 0.0.148 passes Playwright navigate-step URLs to page.goto() without validating the scheme and runs step-based scripts inside the backend container. A signed-in user who can run workflows can navigate to file:// URLs and use getText to read known-path files such as the Kubernetes ServiceAccount token or Docker secrets. |
| CVE-2026-134359 | High | 2026-11-21 | Not applicable | No public exploit | AzuraCast before 0.24.1 fails to escape backslashes in Liquidsoap annotation values, allowing media managers to break out of quoted annotation strings. Attackers can set a crafted ID3 title ending in a backslash to inject a process: protocol URI, achieving OS command execution in the Liquidsoap container during playback. |
| CVE-2026-134356 | Medium | 2026-11-21 | Not applicable | No public exploit | AzuraCast 0.19.0 before 0.24.1 contains an improper authorization vulnerability that allows users with station media rights to add tracks to other stations' playlists by supplying foreign playlist ids to the single-file edit endpoint. Attackers can send sequential playlist ids in the playlists array to inject entries into other stations' AutoDJ rotations and public now-playing metadata, causing failed playback slots. |
| CVE-2026-134355 | Medium | 2026-11-21 | Not applicable | No public exploit | AzuraCast before 0.24.1 contains an improper authorization vulnerability in the /api/station/{station_id}/profile/edit endpoint that exposes and accepts Icecast/Shoutcast passwords for users holding Manage Station Profile without Manage Station Broadcasting. Authenticated station users can read the admin, source, relay and streamer passwords via GET to administer Icecast or broadcast to listeners, or overwrite them via PUT to lock out operators. |
| CVE-2026-134354 | Medium | 2026-11-21 | Not applicable | No public exploit | rclone from 1.59.0 before 1.76.0 contains a confinement escape in the local backend's setXattr function that lets attackers write user.* extended attributes outside the destination root via a planted symlink. Attackers who plant a symlink to an outside directory with a pre-existing child can use --links --metadata operations to set attacker-chosen user.* xattrs on files outside the destination. |
| CVE-2026-134353 | Medium | 2026-11-21 | Not applicable | No public exploit | rclone before 1.76.0 leaks credentials in its swift, netstorage and seafile backends, which follow HTTP redirects using Go's default policy: swift and netstorage send auth headers or passwords on cross-host or HTTPS-to-HTTP redirects, and seafile sends API tokens or passwords on same-host HTTPS-to-HTTP redirects. Attackers receiving or observing a redirect issued by the configured endpoint can capture these credentials to access storage or replay signed requests. |
| CVE-2026-134352 | Critical | 2026-11-21 | Not applicable | No public exploit | Rclone from 1.51.0 before 1.76.0 contains an authentication bypass vulnerability in serve sftp --auth-proxy because the generateCacheKey cache key omits the authentication method. Attackers knowing a victim's base64 public key can submit it as a password from the same client IP to reuse the cached entry and gain read-write VFS access. |
| CVE-2026-134351 | Low | 2026-11-21 | Not applicable | No public exploit | Rclone 1.49.0 before 1.76.0 contains an improper authentication vulnerability in Proxy.Call that lets revoked users keep access because cached auth-proxy answers are never revalidated. Revoked users of serve sftp, ftp, http, or webdav can reconnect within five minutes using their original credentials to retain access indefinitely. |
| CVE-2026-134350 | Medium | 2026-11-21 | Not applicable | No public exploit | rclone 1.67.0 before 1.76.0 contains a credential leak vulnerability in the Ulozto backend that sends X-Auth-Token and X-User-Token headers to unintended hosts on HTTP redirect because downloads use the authenticated f.rest client instead of f.cdn. Attackers who can observe or redirect CDN download traffic can capture the long-lived API key and session token to gain persistent access to the victim's Ulozto storage. |
| CVE-2026-134349 | Medium | 2026-11-21 | Not applicable | No public exploit | Rclone from 1.46.0 before 1.76.0 contains a memory exhaustion vulnerability in the remote control server that allows unauthenticated clients to crash rclone by sending oversized JSON bodies. Attackers can POST large JSON payloads to protected RC methods, which handlePost decodes before authorization checks, triggering out-of-memory termination and interrupting transfers. |
| CVE-2026-134348 | Medium | 2026-11-21 | Not applicable | No public exploit | Rclone from 1.56.0 before 1.76.0 contains a timing side-channel vulnerability in its htpasswd authentication middleware that allows unauthenticated attackers to enumerate valid usernames. Attackers can send HTTP Basic Auth requests with wrong passwords and measure response times, because bcrypt verification runs only for existing users, enabling targeted password guessing. |
| CVE-2026-134347 | High | 2026-11-21 | Not applicable | No public exploit | actix-files before 0.7.4 contains an information disclosure vulnerability that allows remote unauthenticated attackers to read hidden files by requesting Windows 8.3 short-name aliases. Attackers can request short names like ENV~1 or GIT~1/config to bypass the leading-dot check in actix_files::Files and retrieve .env secrets and .git contents. |
| CVE-2026-134342 | Medium | 2026-11-21 | Not applicable | No public exploit | actix-http 3.18.10 before 3.20.2 contains an HTTP request smuggling vulnerability in its chunked decoder, which treats a bare LF after the last chunk as the start of a trailer section. Attackers can send a body ending in 0\r\n\n through a connection-reusing proxy so the next request's body is parsed as new requests, bypassing WAF or upstream protections. |
| CVE-2026-134341 | High | 2026-11-21 | Not applicable | No public exploit | actix-http 3.0.0 before 3.20.3 contains a denial of service vulnerability that allows unauthenticated remote attackers to exhaust memory by sending large-window brotli request bodies. Attackers can send an 850-byte body with Content-Encoding: br declaring a 2^30 window, forcing about 1 GiB of decoder allocation per request and OOM-killing servers. |
| CVE-2026-134339 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB from 26.11.1-SNAPSHOT before 26.11.1 contains an authorization bypass vulnerability that allows authenticated users to skip per-type ACL checks when a database is opened on demand. Attackers can send the first POST /api/v1/batch/{database} request to a closed database to read and write types they are not entitled to access. |
| CVE-2026-134338 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB 25.8.1 before 26.11.1 contains an incorrect authorization vulnerability because per-type ACLs are keyed by type name, renames are not propagated to the permission configuration, and requestAccessOnType allows unknown type names by default. Authenticated users holding only updateSchema can run ALTER TYPE NAME on a denied type to gain read, DELETE and TRUNCATE access, immediately for TIMESERIES types and after the next security rebuild for record-backed types. |
| CVE-2026-134337 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB native-image server builds 26.8.1 before 26.11.1 contain an authorization bypass vulnerability that allows authenticated clients to perform writes through read-only query paths by nesting statements in SELECT. Missing reflection metadata leaves SqlAstInspector with an empty AST, letting INSERT in projections or LET clauses persist via the query endpoint, MCP read-only mode, and HA follower routing. |
| CVE-2026-134335 | Medium | 2026-11-21 | Not applicable | No public exploit | ArcadeDB 21.10.1 before 26.11.1 contains a resource-limit bypass vulnerability that allows restricted users to evade per-group readTimeout because limits are applied to shared cached statements and plans. Attackers can run SQL text previously cached by an unrestricted principal to skip timeouts, or impose their own timeout and limit on root and other users. |
| CVE-2026-134334 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB from 26.7.1 before 26.11.1 contains an information disclosure vulnerability because LSMTreeFullTextIndex computes BM25 corpus statistics over all buckets of the indexed type, ignoring bucket access control on subtypes. Authenticated users with read access to a supertype but not its subtype can run EXPLAIN or PROFILE on full-text queries and read totalDocs and per-term df values to count hidden subtype documents containing chosen terms. |
| CVE-2026-134329 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB 26.2.1 before 26.11.1 contains an observable response discrepancy in MCPToolUtils.resolveDatabase, which checks database existence before authorization and returns distinct 'not authorized' and 'does not exist' errors; separately, a failed Bolt LOGON from READY leaves the previous principal bound after RESET. Authenticated MCP callers can enumerate names of databases they are not granted by probing tools such as query or get_schema. |
| CVE-2026-134327 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB before 26.11.1 contains an authorization bypass vulnerability that allows authenticated users to read schema definitions of denied types through listings ignoring per-type ACLs. Attackers can query the PostgreSQL wire catalog, GraphQL introspection, or MCP get_schema to reveal property names, indexes, inheritance, and materialized view SQL. |
| CVE-2026-134325 | High | 2026-11-21 | Not applicable | No public exploit | ArcadeDB before 26.11.1 contains a denial of service vulnerability in the Redis protocol handler, which neither replies to nor closes a pre-authentication connection when it receives an array whose first element is not a string. Unauthenticated attackers can resend such an array just within the 30-second socket idle timeout to hold connections open indefinitely and exhaust RedisNetworkExecutor threads. |
| CVE-2026-134324 | Medium | 2026-11-21 | Not applicable | No public exploit | ArcadeDB 26.3.1 before 26.11.1 contains a read-only bypass vulnerability that allows server administrators to commit writes through the MCP read-only query tool by submitting Groovy-fallback Gremlin scripts. GremlinQueryEngine.analyze() evaluates scripts like Graph API addVertex calls on the auto or groovy engine and classifies them as READ, persisting writes the read-only restriction should refuse. |
| CVE-2026-134322 | High | 2026-11-21 | Not applicable | No public exploit | better-auth 0.4.12-beta.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication vulnerability in the phone number plugin that lets sign-up and other flows save unverified phone numbers, which phone OTP sign-in then uses to select the account. Attackers can attach a victim's number to an attacker-controlled account so the victim's valid OTP sign-in yields a session for that account, exposing data the victim then enters. |
| CVE-2026-134321 | Low | 2026-11-21 | Not applicable | No public exploit | better-auth from 0.8.1-beta.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and @better-auth/passkey from 1.6.25 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, let revoked sessions stay valid because secondary storage session lists are updated non-atomically and some routes trust cookie-cached sessions. An attacker holding a valid session can evade bulk revocation or bans, or use a revoked cached session to register a passkey or create a lasting session. |
| CVE-2026-134320 | Low | 2026-11-21 | Not applicable | No public exploit | @better-auth/passkey 1.4.0-beta.16 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and the passkey plugin in better-auth 1.2.0-beta.18 before 1.4.0, do not confirm WebAuthn user verification when userVerification is "required" and take the expected origin from the request instead of configuration. Users can register or use passkeys without the required PIN or biometric check, and passkey responses created on another origin under the same relying party ID may be accepted. |
| CVE-2026-134318 | Medium | 2026-11-21 | Not applicable | No public exploit | better-auth 1.5.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a privilege escalation vulnerability in the organization plugin, where the creator role check compares the raw invitation role string while later checks trim it. Admins or other non-creator roles that can invite can submit a padded role such as " owner" that becomes owner on acceptance, allowing deletion of the organization and removal of original owners. |
| CVE-2026-134317 | Medium | 2026-11-21 | Not applicable | No public exploit | @better-auth/stripe 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an authorization bypass vulnerability because the stripeCustomerId user field accepts values from sign-up and update-user requests, letting a user replace their own Stripe customer ID with another customer's. Attackers who know another customer's Stripe ID can open that customer's billing portal to view invoices and billing details, change payment methods, and cancel or modify subscriptions. |
| CVE-2026-134316 | High | 2026-11-21 | Not applicable | No public exploit | @better-auth/electron 1.5.0-beta.12 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 accepts any validly signed value as its transfer cookie and returns the full endpoint context, including the auth secret and social provider client secrets, in sign-in responses. Authenticated users can obtain these secrets to forge sessions as other users. Attackers knowing a password can exchange desktop authorization codes issued before two-factor verification to bypass the second factor. |
| CVE-2026-134315 | High | 2026-11-21 | Not applicable | No public exploit | better-auth 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication vulnerability because email-change links record the old and new addresses but not the requesting user. Attackers can open a still-valid link issued for their own account after a victim registers the attacker's released old address, gaining a session and changing the victim's email to one they control. |
| CVE-2026-134314 | Medium | 2026-11-21 | Not applicable | No public exploit | better-auth 1.3.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition in the emailOTP plugin attempt counter, collision-prone email change code keys, and accent-insensitive email lookups. Unauthenticated attackers can send concurrent guesses exceeding allowedAttempts to brute-force OTPs and sign in or reset passwords, signed-in users can verify addresses they do not own, and attackers receiving mail at accent-variant addresses can reset victims' passwords. |
| CVE-2026-134313 | High | 2026-11-21 | Not applicable | No public exploit | Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition with MySQL or MariaDB serial IDs because the inserted row's ID is read via a separate LAST_INSERT_ID() query that may run on a different pooled connection. Under concurrent load, a user signing in can receive another user's session and act as that user. |
| CVE-2026-134312 | High | 2026-11-21 | Not applicable | No public exploit | Better Auth 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an OAuth sign-in authentication flaw that treats unverified provider emails as verified, including string "false" email_verified claims, unchecked generic OAuth profile/ID-token subject mismatches, and ignored Zoom provider options. Attackers holding a victim's address unverified at an affected provider can sign in, link to the victim's local account, and obtain its session. |
| CVE-2026-134311 | High | 2026-11-21 | Not applicable | No public exploit | better-auth 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an incorrect authorization vulnerability in the admin plugin's /admin/update-user endpoint that lets roles holding user:update change another user's phoneNumber and phoneNumberVerified fields. Attackers can set their own verified phone number on a higher-privileged account and sign in via phone OTP to take it over. |
| CVE-2026-134310 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB from 3.2.0 before 3.3.4 contains an authorization bypass vulnerability that allows record users to update protected rows by exploiting table-level PERMISSIONS FOR update predicates referencing COMPUTED fields. Because check_update_permissions evaluates the predicate before computed fields are populated, the field reads as NONE and deny-intended predicates like blocked != true pass, letting attackers modify records. |
| CVE-2026-134309 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 1.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows authenticated users to shadow protected $access, $auth, and $token variables by binding them as FOR loop variables. Attackers can wrap queries in nested FOR loops with forged values to satisfy table permission predicates, enabling unauthorized reads, modifications, or deletions as a VIEWER. |
| CVE-2026-134307 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains a permission bypass vulnerability that allows authenticated low-privilege database users to read restricted records by calling the GET /export endpoint. Attackers can export raw records that skip table SELECT predicates and field-level SELECT permissions, exposing other users' rows and hidden fields. |
| CVE-2026-134306 | Medium | 2026-11-21 | Not applicable | No public exploit | SurrealDB before 4.0.0 contains an incorrect authorization vulnerability in filter_fields_by_permission that allows authenticated record users to read denied child field values. Attackers can query rows where overlapping items[*] and items[*].secret permissions compact arrays, causing shifted elements to retain field values denied by SELECT permissions. |
| CVE-2026-134303 | High | 2026-11-21 | Not applicable | No public exploit | SurrealKV before 1.1.0 contains an out-of-bounds read vulnerability in the safe InternalKeyRef::from_encoded constructor, which only checks key length with a debug-only assertion. Callers passing keys shorter than 16 bytes, or crafted or corrupted SSTable blocks, trigger unchecked length underflow in timestamp(), seq_num() and trailer(), reading heap bytes before the allocation or panicking. |
| CVE-2026-134302 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 1.0.0 before 4.0.0 contains a denial of service vulnerability that allows any user able to run queries to crash the server by triggering unchecked decimal overflow in math::sum or math::product. Attackers can submit a query summing or multiplying large decimal literals or aggregate stored decimals with GROUP ALL, causing a rust_decimal panic that terminates the entire server process. |
| CVE-2026-134301 | Medium | 2026-11-21 | Not applicable | No public exploit | SurrealDB before 4.0.0 contains a guard bypass vulnerability that allows authenticated users to execute write subqueries by embedding them in LIVE query WHERE clauses or field projections. Attackers can inject CREATE, UPDATE, DELETE, or RELATE statements that run atomically inside other users' triggering transactions, amplifying writes and exfiltrating document data after permission revocation. |
| CVE-2026-134300 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB from 2.2.0 before 4.0.0 contains an authorization bypass vulnerability in Document::purge_references that lets authenticated users bypass target table PERMISSIONS by triggering REFERENCE ON DELETE cascades. Attackers can delete a referenced record to delete, unset, or run CUSTOM expressions on referencing records despite PERMISSIONS FOR delete or update NONE. |
| CVE-2026-134299 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.4 before 4.0.0 does not apply operator-configured WebSocket frame, message, and buffer size limits to the GraphQL WebSocket upgrade handler at GET /graphql, falling back to permissive library defaults. Unauthenticated remote attackers who supply the target namespace and database in request headers can hold up to 64 MiB of in-flight data per concurrent connection, exhausting server memory and degrading availability. |
| CVE-2026-134298 | Medium | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass that allows users with the read-only VIEWER role to modify database schema, because CREATE on a nonexistent table implicitly defines it without the DEFINE TABLE permission check applied to explicit definitions. Authenticated VIEWER users can issue CREATE statements in non-STRICT databases to add arbitrary empty SCHEMALESS tables, cluttering schemas or colliding with application table names. |
| CVE-2026-134295 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in direct filesystem buckets because BucketController::check_permission evaluates key-based ACLs against the un-normalized object key, while FileStore::to_os_path collapses '..' sequences without a traversal check. An authenticated tenant permitted only for certain keys can supply a key such as /public/../private/confidential.txt to read, write, or delete arbitrary files within the storage root. |
| CVE-2026-134294 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in its bucket storage layer on Windows, where ObjectKey::check_no_traversal splits object keys only on forward slashes while FileStore::to_os_path treats backslashes as directory separators. Attackers can supply object keys such as /..\bucket2\secret to bypass the traversal check and read or modify files in other buckets. |
| CVE-2026-134293 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.1.0 before 4.0.0 contains an SQL injection vulnerability in its Model Context Protocol (MCP) server because the identifier validator (consume_backtick_ident and validate_identifier) treats the first backtick as the closing delimiter, ignoring escape characters that the SurrealQL parser honors. Attackers can supply MCP tool arguments containing an escaped backtick to break out of the quoted identifier and execute arbitrary SurrealQL statements. |
| CVE-2026-134292 | Critical | 2026-11-21 | Not applicable | No public exploit | SurrealDB 1.0.0 before 4.0.0 contains a capability check bypass in its embedded JavaScript scripting engine, where the surrealdb.functions bridge calls the internal fnc::synchronous() and fnc::asynchronous() dispatchers without enforcing function capability checks. Authenticated users denied access to built-in functions in SurrealQL can execute them by calling them through surrealdb.functions from embedded JavaScript. |
| CVE-2026-134291 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in its filesystem storage bucket that only canonicalizes the bucket root, not descendant symlinks. Attackers can reference paths through a pre-existing symlink inside the bucket that pass the lexical prefix check, reading and writing files across the host filesystem. |
| CVE-2026-134290 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 2.2.0 before 4.0.0 includes the record id of a referencing row in the error returned when a delete is blocked by an ON DELETE REJECT reference, without checking the caller's SELECT permission on that row. An authenticated principal with DELETE permission can attempt to delete a referenced record and read the rejection error to learn the existence and exact ids of referencing records hidden by row-level SELECT permissions. |
| CVE-2026-134289 | Medium | 2026-11-21 | Not applicable | No public exploit | SurrealDB 1.0.0 before 4.0.0 prints SURREAL_PASS and SURREAL_TOKEN environment variable values in clear text in the --help and -h output of CLI commands such as surreal start, sql, import, export, and mcp, because the arguments do not set clap's hide_env_values. Anyone who later sees that terminal output, for example in shell logs, CI logs, or screen shares, can obtain root database credentials. |
| CVE-2026-134288 | High | 2026-11-21 | Not applicable | No public exploit | SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows clients with table write access to persist writes refused by THROWing table events within interactive transactions. Attackers can run a guarded statement via RPC begin and query, ignore the returned error, and commit to persist the record and event side effects. |
| CVE-2026-134287 | Critical | 2026-11-21 | Not applicable | No public exploit | OpenRemote core before 1.34.0 contains an authentication bypass vulnerability in UserAssetProvisioningMQTTHandler that allows unauthenticated attackers to impersonate provisioned devices without proof of private key possession. Attackers can publish a known device's public certificate to the provisioning request topic, authenticating their anonymous MQTT connection as the device's service account to read and modify assets. |
| CVE-2026-134286 | Medium | 2026-11-21 | Not applicable | No public exploit | OpenRemote from 1.2.0 before 1.34.0 contains an authorization bypass vulnerability in AlarmFacade that allows restricted users with write:rules to create alarms for assets outside their ruleset subtree. Attackers can deploy a JSON asset-scoped ruleset using target.custom asset ids to create HIGH severity alarms and trigger operator notifications about arbitrary in-realm assets. |
| CVE-2026-134284 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 1.0.0 before 2.8.0 contains an account takeover vulnerability that allows attackers to hijack SSO identities by planting local accounts with unverified victim emails. When emailfallback is enabled, attackers register or edit a local account using the victim's email, causing the victim's first OIDC login to link into the attacker-controlled account and expose their data. |
| CVE-2026-134282 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.14.0 before 2.8.0 contains a mass assignment vulnerability that allows authenticated users to set json-hidden fields by sending XML request bodies to the v1 API. Attackers can set BackgroundFileID on project creation to download any stored file via the background endpoint, or create bots with IsAdmin set to gain instance-admin access. |
| CVE-2026-134281 | Medium | 2026-11-21 | Not applicable | No public exploit | Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to read other users' private projects through the tasks.overdue webhook payload. Attackers can register a personal tasks.overdue webhook with one subscribed overdue task, then receive project titles, descriptions, and owner IDs from other users' reminders at external URLs. |
| CVE-2026-134280 | Low | 2026-11-21 | Not applicable | No public exploit | Vikunja 0.17.0 before 2.8.0 builds the task.deleted notification and webhook payload, including related tasks, with the deleting user's permissions and sends it to all project subscribers without per-recipient authorization checks. A user subscribed to a project, or owning its webhook, receives full data of related tasks in private projects they cannot read when a task in their project is deleted. |
| CVE-2026-134279 | Low | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log victims into the attacker's account and view the victims' entered data. |
| CVE-2026-134278 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja 2.3.0 before 2.8.0 contains an uncontrolled memory allocation in the CSV migration module because it does not de-duplicate label column mappings or cap labels per row, and enforces the item limit only after the full import is built. Authenticated users can send one request to /api/v2/migration/csv/migrate with repeated label mappings or many labels per row, exhausting memory until the server is OOM-killed. |
| CVE-2026-134277 | Low | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.16.0 before 2.8.0 contains an information disclosure vulnerability that writes users' Trello API tokens to application logs and Sentry by formatting provider errors verbatim in listeners.go. When a Trello migration fails with a transport error, the URL error embeds the token query parameter, letting anyone with log or telemetry access obtain the reusable third-party credential. |
| CVE-2026-134276 | Medium | 2026-11-21 | Not applicable | No public exploit | Vikunja from 2.2.1 before 2.8.0 contains a TOTP replay protection bypass in ValidateTOTPPasscode that allows attackers to reuse consumed codes by padding them with whitespace. Attackers with valid credentials who observe a used passcode can resubmit it whitespace-padded to the login API within the validity window to obtain a session token. |
| CVE-2026-134275 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.8.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated project readers to amplify response size by repeating requested properties in CalDAV PROPFIND requests. Attackers can send PROPFIND requests to the dav projects endpoint with hundreds of duplicate calendar-data properties to exhaust server memory, CPU, and bandwidth. |
| CVE-2026-134273 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 2.6.0 before 2.8.0 contains a resource exhaustion vulnerability in the Planka migration converter that multiplies task allocations for duplicate list IDs. Attackers controlling a Planka server can return boards with duplicate list IDs and many cards to exhaust memory and OOM-kill the Vikunja process. |
| CVE-2026-134272 | Medium | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators' email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members. |
| CVE-2026-134271 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 1.0.0 before 2.8.0 contains a memory exhaustion vulnerability that allows authenticated users to crash the server by uploading extreme-width images as task attachments. Attackers can request the attachment preview endpoint so Lanczos resampling allocates width-proportional weight tables, OOM-killing the process repeatedly with sub-megabyte PNGs. |
| CVE-2026-134270 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.19.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated CalDAV users to exhaust server CPU by uploading VTODO properties with many parameters. Attackers can PUT an iCalendar body with thousands of parameters on one line to any valid project ID, triggering superlinear parsing before permission checks. |
| CVE-2026-134269 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.18.0 before 2.8.0 contains a resource amplification vulnerability in pkg/models/export.go that allows authenticated users to exhaust server memory by exporting heavily related tasks. Attackers can relate many tasks to one task with a large description and request a user export, causing an out-of-memory crash for all users. |
| CVE-2026-134268 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.21.0 before 2.8.0 contains a resource exhaustion vulnerability that allows authenticated users to trigger instance-wide database writes by setting a project position below 0.1. Attackers can repeatedly send PUT requests to /api/v2/projects/{id} so recalculateProjectPositions updates every user's root projects, holding SQLite's write lock and degrading availability. |
| CVE-2026-134267 | Medium | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.21.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated users to exhaust memory and CPU by creating tasks with many reminders and long titles. Attackers can store a task whose ParseAlarms rendering in pkg/caldav/caldav.go uses quadratic string concatenation, causing every CalDAV read, including other members' automatic syncs, to allocate gigabytes. |
| CVE-2026-134266 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 0.19.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated users to exhaust CPU by supplying unbounded business-day operands in datemath filters. Attackers can send task or time-tracking filters like due_date > now+999999999999b, triggering a per-day loop in go-datemath that pins CPU cores and exhausts the server. |
| CVE-2026-134265 | High | 2026-11-21 | Not applicable | No public exploit | Vikunja from 2.4.0 before 2.8.0 contains a denial of service vulnerability in the richtext converter that allows authenticated project writers to exhaust server memory and CPU by storing tables with unbounded rowspan and colspan values. Any project reader or CalDAV client can trigger the expansion through markdown task reads, CalDAV GETs, or the frontend editor, producing 100 MB responses from a 64-byte description. |
| CVE-2026-134264 | High | 2026-11-21 | Not applicable | No public exploit | Admidio from 5.0.2 before 5.0.17 contains an arbitrary file read vulnerability that allows any logged-in member to read server files by placing local paths in img src attributes of eCard messages. Attackers can send an eCard to their own account so sendEcard() embeds files like adm_my_files/config.php via addEmbeddedImage(), disclosing database credentials and /etc/passwd. |
| CVE-2026-134262 | Critical | 2026-11-21 | Not applicable | No public exploit | Admidio 5.0.0 before 5.0.18 contains a stored cross-site scripting vulnerability that allows role administrators to inject JavaScript by placing quote-breaking payloads in role names rendered unencoded in the data-message attribute in modules/profile/roles_functions.php. Attackers can execute scripts when a full administrator views an affected profile page, stealing the CSRF token to assign themselves the Administrator role. |