Overview 168,474 matches · 7,783 in Waratek scope · 521 protected · 957 exploited · 182 CISA KEV · 9,886 public PoC · 630 EPSS ≥ 0.5
168,474matches
7,783in Waratek scope4.6%
521protected0.3%
957exploited0.6%
182CISA KEV0.1%
9,886public PoC5.9%
630EPSS ≥ 0.50.4%
Protected by Waratek
522
0.3%
Rule in development
2
0.0%
Mitigation candidate
177
0.1%
No exploit published
7,082
4.2%
Outside Waratek scope
2,544
1.5%
Not applicable
158,147
93.9%
Withdrawn CVE
0
0.0%
split by
peak 36,369 / year
2005524
Mitigation candidate1
No exploit published22
Not applicable501
Medium524
not blocked524
Exploited3
Working exploit published153
Forecast only1
No public exploit367
20063,324
Protected by Waratek4
Mitigation candidate4
No exploit published48
Outside Waratek scope3
Not applicable3,265
Medium3,324
blocked by ARMR today4
not blocked3,320
Exploited10
Working exploit published1,137
Forecast only2
No public exploit2,175
20073,101
Protected by Waratek2
Mitigation candidate9
No exploit published60
Outside Waratek scope53
Not applicable2,977
Medium3,101
blocked by ARMR today2
not blocked3,099
Exploited14
Working exploit published1,052
Forecast only1
No public exploit2,034
20082,582
Protected by Waratek4
Mitigation candidate8
No exploit published71
Outside Waratek scope26
Not applicable2,473
Medium2,582
blocked by ARMR today4
not blocked2,578
Exploited7
Working exploit published987
Proof of concept only2
Forecast only1
No public exploit1,585
20092,786
Protected by Waratek5
Mitigation candidate9
No exploit published115
Outside Waratek scope31
Not applicable2,626
Medium2,786
blocked by ARMR today5
not blocked2,781
Exploited16
Working exploit published1,123
Proof of concept only2
Forecast only3
No public exploit1,642
20102,241
Protected by Waratek6
Mitigation candidate9
No exploit published118
Outside Waratek scope34
Not applicable2,074
Medium2,241
blocked by ARMR today6
not blocked2,235
Exploited14
Working exploit published547
Proof of concept only1
Forecast only2
No public exploit1,677
20112,101
Protected by Waratek4
Mitigation candidate3
No exploit published132
Outside Waratek scope58
Not applicable1,904
Medium2,101
blocked by ARMR today4
not blocked2,097
Exploited9
Working exploit published294
Proof of concept only3
Forecast only1
No public exploit1,794
20123,035
Protected by Waratek5
Mitigation candidate17
No exploit published177
Outside Waratek scope50
Not applicable2,786
Medium3,035
blocked by ARMR today5
not blocked3,029
not established1
Exploited20
Working exploit published475
Proof of concept only2
Forecast only42
No public exploit2,496
20132,914
Protected by Waratek12
Mitigation candidate12
No exploit published225
Outside Waratek scope155
Not applicable2,510
Medium2,914
blocked by ARMR today12
not blocked2,901
not established1
Exploited23
Working exploit published237
Proof of concept only1
Forecast only6
No public exploit2,647
20145,314
Protected by Waratek32
Mitigation candidate9
No exploit published215
Outside Waratek scope165
Not applicable4,893
Medium5,314
blocked by ARMR today32
not blocked5,282
Exploited24
Working exploit published415
Proof of concept only7
Forecast only12
No public exploit4,856
20153,501
Protected by Waratek20
Mitigation candidate1
No exploit published205
Outside Waratek scope126
Not applicable3,149
Medium3,501
blocked by ARMR today20
not blocked3,481
Exploited23
Working exploit published254
Proof of concept only7
Forecast only8
No public exploit3,209
20162,446
Protected by Waratek25
Mitigation candidate4
No exploit published292
Outside Waratek scope51
Not applicable2,074
Medium2,446
blocked by ARMR today25
not blocked2,420
not established1
Exploited16
Working exploit published122
Proof of concept only6
Forecast only9
No public exploit2,293
20175,687
Protected by Waratek24
Mitigation candidate5
No exploit published326
Outside Waratek scope124
Not applicable5,208
Medium5,687
blocked by ARMR today24
not blocked5,663
Exploited18
Working exploit published332
Proof of concept only21
Forecast only2
No public exploit5,314
20186,163
Protected by Waratek51
Mitigation candidate8
No exploit published428
Outside Waratek scope177
Not applicable5,499
Medium6,163
blocked by ARMR today51
not blocked6,112
Exploited38
Working exploit published348
Proof of concept only27
Forecast only7
No public exploit5,743
20197,117
Protected by Waratek35
Mitigation candidate14
No exploit published405
Outside Waratek scope263
Not applicable6,400
Medium7,117
blocked by ARMR today34
partly blocked1
not blocked7,082
Exploited47
Working exploit published297
Proof of concept only30
Forecast only9
No public exploit6,734
20207,359
Protected by Waratek35
Mitigation candidate15
No exploit published496
Outside Waratek scope286
Not applicable6,527
Medium7,359
blocked by ARMR today35
not blocked7,324
Exploited58
Working exploit published197
Proof of concept only37
Forecast only10
No public exploit7,057
20218,137
Protected by Waratek29
Mitigation candidate11
No exploit published291
Outside Waratek scope259
Not applicable7,547
Medium8,137
blocked by ARMR today29
not blocked8,108
Exploited86
Working exploit published240
Proof of concept only90
Forecast only44
No public exploit7,677
20229,908
Protected by Waratek58
Mitigation candidate3
No exploit published570
Outside Waratek scope211
Not applicable9,066
Medium9,908
blocked by ARMR today58
not blocked9,850
Exploited73
Working exploit published270
Proof of concept only953
Forecast only34
No public exploit8,578
202311,824
Protected by Waratek29
Mitigation candidate10
No exploit published440
Outside Waratek scope144
Not applicable11,201
Medium11,824
blocked by ARMR today29
not blocked11,795
Exploited97
Working exploit published237
Proof of concept only2,408
Forecast only26
No public exploit9,056
202418,998
Protected by Waratek19
Mitigation candidate5
No exploit published320
Outside Waratek scope149
Not applicable18,505
Medium18,998
blocked by ARMR today19
not blocked18,979
Exploited129
Working exploit published114
Proof of concept only3,597
Forecast only10
No public exploit15,148
202523,043
Protected by Waratek37
Rule in development2
Mitigation candidate14
No exploit published471
Outside Waratek scope83
Not applicable22,436
Medium23,043
blocked by ARMR today37
not blocked23,006
Exploited127
Working exploit published170
Proof of concept only5,244
Forecast only5
No public exploit17,497
202636,369
Protected by Waratek86
Mitigation candidate6
No exploit published1,655
Outside Waratek scope96
Not applicable34,526
Medium36,369
blocked by ARMR today86
not blocked36,283
Exploited105
Working exploit published116
Proof of concept only6,785
No public exploit29,363
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-98100 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can import documents in the HWP format, including pictures that link to an external file. An out-of-bounds read existed when the link target of a crafted picture was read, so memory past the picture data could end up in the converted document. In fixed versions the link target is taken only from the picture data. |
| CVE-2026-97999 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Base documents can hold an embedded HSQLDB database. When the experimental features option is enabled, LibreOffice offers to migrate such a database to the embedded Firebird engine when the document is opened. A heap buffer overflow existed when binary values were copied during the migration, because a value could be longer than the space set aside for its column. In fixed versions that space is enlarged whenever a value is longer than its column. |
| CVE-2026-97894 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Calc can open spreadsheets in the DIF format, and text files such as CSV in the UTF-16 encoding. Both are read one line at a time. An out-of-bounds read existed when a line of a crafted file was read, because the length of the line could be miscalculated, so memory beyond the line could be copied into the imported document. In fixed versions each line is read up to its limit and no further. |
| CVE-2026-97892 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice checks the digital signatures of a PDF document when the document is opened, and shows whether each signature is valid. An out-of-bounds write existed when a signature was checked, because the parts of the file that a crafted signature claims to cover were not checked against the size of the file. In fixed versions a signature that claims to cover anything outside the file is reported as not valid. |
| CVE-2026-93673 | Medium | 2026-11-16 | Not applicable | No public exploit | The Zephyr WebSocket client validates the server's handshake response in on_header_value() in subsys/net/lib/websocket/websocket.c. The comparison was performed as strncmp(at, str, length), where length is the length of the value the server sent rather than the length of the expected value, so the check only asked whether the received value was a prefix of the expected base64(SHA-1(key || GUID)). A server that returned a handful of correct characters passed, and a response carrying an empty Sec-WebSocket-Accept: header caused strncmp() to be called with a count of zero, which returns 0 and set ctx->sec_accept_ok with no comparison performed at all. The header-value callback also cleared ctx->sec_accept_present after the first chunk, so a value split across receive-buffer boundaries was only ever examined in part. ctx->sec_accept_ok is the sole WebSocket-specific gate in websocket_connect(); the client does not check the HTTP status code or the Upgrade:/Connection: headers. Any HTTP response containing an empty or prefix-matching Sec-WebSocket-Accept header therefore completed the handshake, after which the socket is finalized as a WebSocket and all further peer bytes are parsed as frames. The affected path is driven directly by remote input through subsys/net/lib/http/http_parser.c, and is reached by every user of websocket_connect(), including MQTT over WebSocket (subsys/net/lib/mqtt/mqtt_transport_websocket.c) and subsys/net/lib/ocpp/ocpp.c. The Sec-WebSocket-Accept exchange is not a secret-based authentication -- an endpoint or on-path attacker that sees the request can compute the expected value -- so the impact is bounded to parties that never observed the handshake request: a caching or transparent intermediary replaying a canned response, an off-path attacker injecting a spoofed response, or a non-WebSocket endpoint the client was induced to talk to. For those, the per-connection binding that RFC 6455 requires the client to enforce provided no protection at all, letting a single crafted response convince the device it holds a live WebSocket session and causing it to send application data to, and accept frames from, an unverified peer. There is no memory-safety consequence. The fix compares each delivered chunk against the expected value at the position reached so far, refuses a chunk that would overrun it, and accepts only once every byte of the expected value -- and no more -- has been matched; on_header_field() now also clears the flag for any other header so a partial value cannot be continued across an intervening header. |
| CVE-2026-93672 | Medium | 2026-11-16 | Not applicable | No public exploit | bt_att_find_req_by_user_data() in subsys/bluetooth/host/att.c walks every ATT channel attached to a connection and dereferences chan->req->user_data without checking chan->req. An ATT channel with no client request in flight holds chan->req == NULL — that is its normal idle state, set by att_handle_rsp() when a response resolves the transaction and tested by att_req_send_process() to pick a free channel — so the lookup reads through a NULL pointer as soon as it visits an idle channel. Every other chan->req user in the file already guards the pointer. The lookup is reached from the public bt_gatt_cancel() API and, more importantly, from the host itself: bt_gatt_unsubscribe() calls bt_gatt_cancel() while a subscribe CCC write is still outstanding (BT_GATT_SUBSCRIBE_FLAG_WRITE_PENDING), and call_notify_cb_and_maybe_unsubscribe() in subsys/bluetooth/host/gatt.c invokes bt_gatt_unsubscribe() from the RX path whenever an application notify callback returns BT_GATT_ITER_STOP. A malicious or malfunctioning peer can hold the trigger window open by withholding the ATT Write Response to the CCC write and then sending a notification for the subscribed handle. With CONFIG_BT_EATT the traversal is very likely to meet an idle sibling channel, since ATT channels are prepended to the list and a channel opened after the pending request was sent is visited first. The dereference is a read of a small constant offset from address zero, so the impact is availability only: no memory corruption, no attacker-chosen address and no information disclosure. On platforms and configurations where a near-NULL read traps — TrustZone non-secure images, MMU targets, native_sim, or builds with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU/_DWT — the fault occurs in the Bluetooth RX context and results in a fatal error and device reset. On a plain Cortex-M build with the vector table mapped at address 0 and null-pointer detection disabled (the default) the read succeeds and the defect is inert. The fix adds an explicit chan->req != NULL test to the channel traversal and additionally rejects a NULL user_data argument, which would otherwise have matched, and cancelled, an unrelated request. |
| CVE-2026-93669 | Medium | 2026-11-16 | Not applicable | No public exploit | The ITE IT8xxx2 SHI host-command backend in subsys/mgmt/ec_host_cmd/backends/ec_host_cmd_backend_shi_ite.c arms the SPI peripheral before its receive context exists. shi_ite_init_registers() sets the state machine to SHI_STATE_READY_TO_RECV and calls irq_enable() while the device initializes at POST_KERNEL priority CONFIG_KERNEL_INIT_PRIORITY_DEFAULT (40), but data->rx_ctx and data->tx are only assigned later by shi_ite_backend_init(), which ec_host_cmd_init() invokes at CONFIG_EC_HOST_CMD_INIT_PRIORITY (default 80). If the attached host processor starts a SPI transaction inside that window, the Rx-valid-length interrupt fires, shi_ite_int_handler() passes its state check and calls shi_ite_parse_header(), which stores the host-derived request length through the still-NULL data->rx_ctx. On the IT8xxx2 low addresses are not backed by RAM, and with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_PMP the first bytes of the address space are explicitly made inaccessible, so the store raises a fatal access fault in interrupt context. The window widens further when CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT is disabled and the application calls ec_host_cmd_init() itself. The result is a kernel panic on the embedded controller: with Zephyr's default fatal handler the CPU halts, so the controller stops servicing host commands until a hardware reset. Because the trigger is traffic from the attached host processor -- an untrusted peer from the controller firmware's point of view -- software on that host can provoke the fault by forcing a controller reset and issuing transactions during the reboot, turning a recoverable reset into a persistent outage. Impact is limited to availability: the faulting address is fixed and not attacker-chosen, so no memory-corruption primitive follows. The fix leaves the interface at SHI_STATE_DISABLED with the interrupt masked during device init, moves irq_enable() into shi_ite_backend_init() after the buffers are published, and makes shi_ite_int_handler() reject a NULL data->rx_ctx while write-clearing IT83XX_SPI_ISR and IT83XX_SPI_RX_VLISR so that an unexpected early interrupt cannot storm. |
| CVE-2026-93668 | Medium | 2026-11-16 | Not applicable | No public exploit | The Bluetooth Classic SDP server in subsys/bluetooth/host/classic/sdp.c allocated every response PDU through bt_sdp_create_pdu(), which expands to bt_l2cap_create_pdu() and therefore uses a K_FOREVER timeout. The allocation is made from sdp_pool, a fixed pool holding only CONFIG_BT_MAX_CONN buffers (one in the default configuration) that is shared with the SDP client role. When the pool is empty the call blocks without a bound. The allocation is reached from bt_sdp_recv() on the Bluetooth host's RX context: the bt_workq "BT RX WQ" workqueue in the default configuration since v3.1.0, and the dedicated "BT RX" thread before that. This context processes all normal-priority HCI events and all received ACL data. The SDP L2CAP server is registered on PSM 0x0001 with no security requirement (BT_SECURITY_L0), so an unpaired, unauthenticated BR/EDR peer within radio range of a connectable device can drive it. Every malformed or unrecognised SDP PDU reaches send_err_rsp(), and the sdp_svc_search_req(), sdp_svc_att_req() and sdp_svc_search_att_req() handlers allocate as well, so a short burst of pipelined requests drains the pool and parks the RX context in the blocking allocation. A pool buffer is released only once its response has been sent, and a peer that withholds baseband acknowledgements keeps the controller's buffers for the link full, so the response is never sent. While the RX context is blocked, the entire Bluetooth host, for all connections and both LE and BR/EDR, stops processing normal-priority HCI events and received data. In most affected releases the stall is permanent. Queued PDUs are freed only by connection or channel teardown, which waits for the normal-priority Disconnection Complete handler, and that handler runs on the blocked RX context, so the host does not recover without a reset. In v3.7.0 through v4.1.x the TX processor discards the queued response once the link supervision timeout drops the connection, so each stall ends at that timeout, but the peer can reconnect and repeat it for as long as it stays in range. The impact is limited to availability; no memory corruption or information disclosure is involved. The fix adds sdp_svc_create_pdu() using K_NO_WAIT, pre-allocates the response buffer once in bt_sdp_recv(), stashes the request in sdp->recv_pending when no buffer is available, and retries it from a work handler once a buffer is freed by the pool destroy callback. |
| CVE-2026-93667 | Medium | 2026-11-16 | Not applicable | No public exploit | The Virtual L2 receive handler virtual_recv() in subsys/net/l2/virtual/virtual.c ends with a fall-through path meant for a virtual interface that has nothing attached below it: it takes net_if_get_device(iface)->api, treats it as a struct virtual_interface_api, and calls api->recv(iface, pkt). That handler is however also invoked with a non-virtual interface: ethernet_recv() in subsys/net/l2/ethernet/ethernet.c deliberately passes the Ethernet interface so that a tagged frame can be dispatched over the VLAN interfaces attached to it. For an Ethernet interface dev->api is a struct ethernet_api, whose layout only shares the leading struct net_if_api, so the slot read as recv is actually get_config() (default) or get_capabilities() (when CONFIG_NET_STATISTICS_ETHERNET is enabled). The fall-through is reached whenever no attached virtual interface claims the frame - most simply when the VLAN interface owning the frame's tag exists but is administratively down, since net_eth_get_vlan_iface() resolves the tag without checking link state while virtual_recv() skips interfaces that are not up. Any host able to place an 802.1Q-tagged Ethernet frame on the same link can then trigger the mistyped indirect call; no authentication, IP reachability or user interaction is required, because the frame is consumed at L2 before any address check. The resulting call passes a struct net_if where the driver expects a struct device and a struct net_pkt where it expects a struct net_if , with the callee's remaining parameters left as whatever the call site happens to leave in the argument registers. Driver implementations dereference these values: get_capabilities() typically reads dev->config/dev->data (a wild read through a non-pointer field of struct net_if), and get_config() implementations write through the uninitialized struct ethernet_config * argument. The practical impact is undefined behaviour in the network RX path - crashes and uncontrolled memory corruption - plus mis-handling of the packet when a capability bitmask is returned as a net_verdict. The attacker controls neither the corrupted address nor the value written, so this is a denial-of-service and memory-corruption issue rather than a controllable write primitive. The same defective fall-through is reachable through any_recv() in subsys/net/l2/dummy/any/any.c, which passes a dummy interface whose struct dummy_api is shorter than the offset read, producing an out-of-bounds read of the driver's API object followed by an indirect call. The fix drops any packet whose interface is not a Virtual L2 interface, closing both entry points. |
| CVE-2026-93666 | Medium | 2026-11-16 | Not applicable | No public exploit | The Bluetooth Classic SDP client built its outgoing request PDUs with bt_sdp_create_pdu(), which allocates from the sdp_pool net-buf pool with a K_FOREVER timeout and no failure handling, in sdp_client_ss_search(), sdp_client_sa_search() and sdp_client_ssa_search() in subsys/bluetooth/host/classic/sdp.c. All of these run on the Bluetooth workqueue bt_workq (via sdp_client_work_handler(), the L2CAP sdp_client_connected() callback, or the continuation-state follow-up from a received response), which is the same single thread that dispatches incoming HCI ACL and event traffic, drives L2CAP, and performs connection and channel teardown. sdp_pool holds only CONFIG_BT_MAX_CONN buffers (one by default) and is shared with the SDP server role. An unauthenticated peer within BR/EDR range can drive both halves of the trigger. The SDP L2CAP server is registered at BT_SECURITY_L0, so any inbound SDP request makes the device allocate the pool's buffer for a response, which is held until the controller has transmitted it. The same peer can then cause a client request to be issued while the pool is empty: in-tree profiles start SDP discovery from inbound connection callbacks (for example hfp_hf_accept() calls bt_sdp_discover() through hfp_hf_create(), and hfp_ag.c mirrors this), and a peer acting as an SDP server can force repeated client requests by answering with partial responses carrying continuation state. With the pool empty, the allocation blocks uninterruptibly and freezes the entire Bluetooth host. The stall becomes permanent when the release of the outstanding buffer itself depends on the blocked workqueue: if the link carrying the queued PDU is dropped or stalls, hci_disconn_complete() and the L2CAP channel cleanup that purges the channel TX queue are themselves bt_workq work items, so the buffer is never returned. The result is an unrecoverable denial of service of all Bluetooth functionality until reboot; there is no memory-safety, confidentiality or integrity impact. The fix allocates client PDUs with K_NO_WAIT via a new sdp_client_create_pdu(), propagates -ENOBUFS, parks the session on a new SDP_CLIENT_FLAG_WAIT_FOR_TX_BUF flag, and adds an sdp_pool destructor that re-submits the SDP client worker when a buffer becomes available. Note that the SDP server role still allocated from the same pool with K_FOREVER at this commit; that path was addressed separately. |
| CVE-2026-91114 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, PermissionCheckboxSetField accepts permission codes that the field did not offer and stores them without an allowlist, then renders permission codes without escaping them. A user with access to the Security section can save attacker-controlled content as a permission code, causing JavaScript to execute in the browser of another user who views the field. This issue is fixed in version 6.2.13. |
| CVE-2026-91113 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit a record through a GridField detail form can submit a user-controlled ClassName value to change the record into an unrelated class without the create and edit permission checks required for that target class. This permits an unauthorized record type change outside the GridField's intended model hierarchy. This issue is fixed in version 6.2.13. |
| CVE-2026-91112 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a user with CMS_ACCESS_SecurityAdmin but without ADMIN can edit or reparent a group that grants ADMIN-equivalent permissions through an assigned role or a parent group, thereby escalating to full administrative privileges. This issue is fixed in version 6.2.13. |
| CVE-2026-91110 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not normalize certain control bytes that browsers ignore when parsing URLs. A CMS author can place those bytes before a javascript: URL in stored content so the sanitiser misses the dangerous scheme, and JavaScript executes in the browser of another user who views the content. This issue is fixed in version 6.2.13. |
| CVE-2026-88989 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, a CMS user who can edit records through a GridField detail form can send a direct save request that creates a new record even when the user does not have permission to create that record type. The server-side save path checks edit access but does not enforce the required create permission before persistence. This issue is fixed in version 6.2.13. |
| CVE-2026-88988 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove SVG data URIs from stored CMS content even though SVG documents can execute script. A CMS author can save such content, and JavaScript executes in the browser of another user who views it. This issue is fixed in version 6.2.13. |
| CVE-2026-88987 | Medium | 2026-11-16 | Not applicable | No public exploit | Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not remove script-capable XHTML and XML data URIs from stored CMS content. A CMS author can save such content, and JavaScript executes in the browser of another user who views it. This issue is fixed in version 6.2.13. |
| CVE-2026-88019 | Medium | 2026-11-16 | No exploit published | No public exploit | When Apache Shiro is used with the Jakarta EE integration module, the automatic form saving feature weakens the security of a form that is resubmitted after login. Cookies set by the application during the resubmission could lose their security attributes, such as `Secure` and `SameSite`. In addition, the resubmitted form data and cookies could be sent to an untrusted host. This issue affects Apache Shiro from 2.0.0-alpha through 3.0.1, only when using `shiro-jakarta-ee` integration module with form saving enabled (the default). Mitigation: Upgrade to version 3.0.2 or later, which no longer replays the form over the network, and avoids this class of issues entirely. Alternatively, you can set the `org.apache.shiro.form-resubmit-host` (String) and `org.apache.shiro.form-resubmit-port` (Integer) system properties to restrict the host and port that Shiro will connect to when resubmitting a form. |
| CVE-2026-87932 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice Writer can save documents in DOCX format. A document can contain content controls whose values are bound to custom XML data, and that data is updated with the current values when the document is exported, including in a conversion run from the command line. Values taken from the document were not escaped where they were used, so a crafted document could write a file of its choosing anywhere the user can write when it was exported to DOCX. In fixed versions these values are written into the document directly, and the XSLT transformations LibreOffice runs can no longer write files or use the network. |
| CVE-2026-87027 | Medium | 2026-11-16 | Not applicable | No public exploit | In EDB Postgres Extended Server and EDB Postgres Advanced Server versions 15 through 18 with Transparent Data Encryption (TDE) enabled, the key used to encrypt temporary files was incompletely initialized. The code applied sizeof() to a pointer to the key buffer rather than to the buffer itself, so only 8 of the intended 32 bytes were filled from a secure random source and the remaining 24 bytes kept whatever was already in memory. This reduces the guaranteed randomness of the temporary-file key from 256 bits to 64 bits. Exploiting this requires local read access to the server's temporary-file directory, and those files normally exist only while the server is running; they persist only after a crash and are removed at the next server start. Permanent data files and WAL are not affected. The issue is fixed in EDB Postgres Extended Server 15.20, 16.16, 17.12 and 18.7 and EDB Postgres Advanced Server 15.20.0, 16.16.0, 17.12.0 and 18.7.0; the server must be restarted after upgrading. |
| CVE-2026-85240 | Medium | 2026-11-16 | Not applicable | No public exploit | Mattermost Desktop App versions <=6.3 6.0.3 6.3.2.0 fail to handle filesystem errors that can occur when finalizing certain file downloads, which allows a malicious or compromised server to cause a denial of service by crashing the entire desktop application via a specially crafted download Mattermost Advisory ID: MMSA-2026-00779 |
| CVE-2026-84234 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can open PDF files in Draw, where the PDF import converts each page into drawing objects that can be edited. Images in the PDF, including images with a transparency mask, are converted along the way. An out-of-bounds write existed when an image with a transparency mask was converted, because positions taken from a crafted image were not checked against the size of the image buffer. In fixed versions the image size is limited, and the position of each mask pixel is checked before it is written. |
| CVE-2026-76822 | Medium | 2026-11-16 | Not applicable | No public exploit | OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the caseIncidentAdd, caseRfiAdd, and caseRftAdd GraphQL mutations require only authentication and do not require a capability check. An authenticated user with reader-level permissions can therefore create incident, request-for-information, and request-for-takedown case objects regardless of the user's assigned role, causing unauthorized changes to platform data. This issue is fixed in version 7.260701.0. |
| CVE-2026-74763 | Medium | 2026-11-16 | No exploit published | No public exploit | Authorization annotations, such as @RequiresRoles and @RequiresPermissions, are not always enforced in some class or interface hierarchies. Annotations declared on an interface were not enforced when using the shiro-guice, shiro-aspectj, shiro-cdi or shiro-jakarta-ee modules. In addition, annotations declared on a class or a superclass were not always enforced when using shiro-guice or shiro-aspectj, allowing an unauthorized caller to invoke methods that should be protected. This issue affects all Apache Shiro versions through 3.0.1, with impact depending on module and where annotations are declared. Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue. The annotation closest to the invoked method now takes precedence. Alternatively, declare authorization annotations directly on each protected implementing method. |
| CVE-2026-74762 | Medium | 2026-11-16 | No exploit published | No public exploit | Apache Shiro is vulnerable to session fixation when a user is authenticated via the "Remember me" functionality. In affected versions, when a subject is restored from a "Remember me" cookie, the existing session is not invalidated, nor is a new session created with a new ID. Additionally, session IDs were accepted from the request URL even when session ID URL rewriting was disabled. This issue affects all Apache Shiro versions through 3.0.0, only when RememberMe functionality is enabled. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by invalidating the existing session and creating a new session with a new ID when a subject is restored from a "Remember me" cookie, and by ignoring session IDs in the URL when URL rewriting is disabled. |
| CVE-2026-71306 | Medium | 2026-11-16 | Not applicable | No public exploit | Mikochi is a minimalist file manager with streaming capabilities. Prior to 1.10.1, authenticated users of bare-metal instances configured with a non-default trailing-slash DATA_DIR can use the Move endpoint to supply traversal-containing source or destination paths. The affected path validation can resolve those paths outside the configured data directory, allowing files to be written beyond Mikochi's intended storage boundary. Docker deployments that confine the data directory to a mounted volume and configurations whose DATA_DIR lacks a trailing slash are not affected by the described attack. This issue is fixed in version 1.10.1. |
| CVE-2026-69221 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Faust.js is a headless WordPress toolkit. Prior to 1.8.12, the FaustWP generateAuthorizationCode GraphQL mutation called wp_authenticate_username_password and wp_authenticate_email_password directly instead of using wp_authenticate. This bypassed callbacks registered on WordPress's outer authenticate filter, including policies for multifactor authentication, single sign-on, IP allowlists, or disabled accounts. On a site using FaustWP local login and one of those policies, an attacker with a valid username or email and password could obtain an authorization code and exchange it through /api/faust/auth/token for access and refresh tokens even when the normal WordPress login path would deny access. This issue is fixed in version 1.8.12. |
| CVE-2026-64890 | Medium | 2026-11-16 | Not applicable | No public exploit | : Cleartext Storage of Sensitive Information vulnerability in Johnson Controls Open Blue Companion Android App on Android allows : Retrieve Embedded Secrets from Software. This issue affects Open Blue Companion Android App: before R2.22.0. |
| CVE-2026-63672 | Medium | 2026-11-16 | Not applicable | No public exploit | EGroupware is a web-based groupware server written in PHP. Prior to 23.1.20260601 and 26.6.20260616, login() in api/src/Auth/Saml.php accepts the unauthenticated idp request parameter when it merely begins with the HTTPS scheme and passes it to SimpleSAMLphp's requireAuth() without checking the configured trusted identity providers. A malicious actor can redirect the sign-in flow to an attacker-controlled identity provider, enabling credential phishing and, when the SimpleSAMLphp deployment does not strictly validate identity-provider metadata, forged SAML assertions as arbitrary users, including administrators. This issue is fixed in versions 23.1.20260601 and 26.6.20260616. |
| CVE-2026-63246 | Medium | 2026-11-16 | Not applicable | No public exploit | A kernel pool buffer overflow vulnerability in the ct0531fl.sys file of the Creative WDM Audio Driver (64-bit), Sound Blaster Audigy 4 and Sound Blaster Audigy 5/Rx could allow a local attacker with low privilege access to cause a denial of service. |
| CVE-2026-57151 | Medium | 2026-11-16 | Not applicable | No public exploit | GLPI is a free asset and IT management software package. From 11.0.0 until 11.0.10 and 12.0.1, an authenticated technician can modify the two-factor authentication security of a user with higher privileges because the affected operations do not enforce all required authorization checks for the target user. This allows the technician to disable or take control of the higher-privileged user's two-factor authentication protection. This issue is fixed in versions 11.0.10 and 12.0.1. |
| CVE-2026-45016 | Medium | 2026-11-16 | Not applicable | No public exploit | EGroupware is a web-based groupware server written in PHP. Prior to 23.1.20260601 and 26.5.20260507, the processURL2InlineImages logic in api/src/Mail.php treats non-HTTP image sources in an HTML mail body as local paths and passes a decoded attacker-controlled file:// URI to file_get_contents. Any authenticated user with mail access can cause files readable by the web server process to be embedded as inline MIME attachments in outgoing email, exposing local configuration, credentials, private keys, or other server files. This issue is fixed in versions 23.1.20260601 and 26.5.20260507. |
| CVE-2026-32789 | Medium | 2026-11-16 | Not applicable | No public exploit | An out-of-bounds read vulnerability exists in VideoLAN VLC 3.0.23. By using a specially crafted NUV file, an attacker could exploit this vulnerability to perform an out-of-bounds read, potentially leading to the disclosure of sensitive information. |
| CVE-2026-28731 | Medium | 2026-11-16 | Not applicable | No public exploit | A memory corruption vulnerability exists in VideoLAN VLC 3.0.23. A specially crafted Interplay MVE file can trigger a condition that allows access to a variable that is not explicitly initialized, which under certain conditions can lead to code execution in the context of the current process. |
| CVE-2026-21177 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Settings Suggestions prior to One UI 8.5 allows local attackers to automatically launch an application in the background. User interaction is required for triggering this vulnerability. |
| CVE-2026-21174 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass APK verification. |
| CVE-2026-21173 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to initiate an unauthorized APK restoration. |
| CVE-2026-21172 | Medium | 2026-11-16 | Not applicable | No public exploit | Incomplete cleanup in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to establish an unauthorized connection. |
| CVE-2026-21171 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper initialization in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass user authorization. User interaction is required for triggering this vulnerability. |
| CVE-2026-21170 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper enforcement of behavioral workflow in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to write arbitrary files with Smart Switch privilege. |
| CVE-2026-21169 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Smart Switch prior to version 3.7.74.1 allows adjacent attackers to install arbitrary applications. User interaction is required for triggering this vulnerability. |
| CVE-2026-21168 | Medium | 2026-11-16 | Not applicable | No public exploit | External control of system or configuration setting in Smart Switch prior to version 3.7.74.7 allows local attackers to bypass required user interaction. |
| CVE-2026-21166 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authentication in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to install arbitrary applications. |
| CVE-2026-21165 | Medium | 2026-11-16 | Not applicable | No public exploit | Insufficient session expiration in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass device authentication. User interaction is required for triggering this vulnerability. |
| CVE-2026-21164 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper handling of insufficient permission in Samsung Pay for Galaxy Watch prior to version 8.0.53 allows local attackers to install arbitrary applications. |
| CVE-2026-21163 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Bixby prior to version 4.1.20 allows remote attackers to launch arbitrary activity with Bixby privilege. |
| CVE-2026-21162 | Medium | 2026-11-16 | Not applicable | No public exploit | Out-of-bounds write in libiosotglib.so prior to version 3.7.73.4 allows physical attackers to execute arbitrary code. User interaction is required for triggering this vulnerability. |
| CVE-2026-21161 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper input validation in Samsung Members prior to version 5.8.20.31 allows local attackers to launch arbitrary activity with Samsung Members privilege. |
| CVE-2026-21160 | Medium | 2026-11-16 | Not applicable | No public exploit | Cross-site request forgery in Samsung Health prior to version 7.1.0.053 allows remote attackers to access sensitive information. User interaction is required for triggering this vulnerability. |
| CVE-2026-21159 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in Samsung Pass prior to version 5.2.12.7 allows physical attackers to access sensitive information. |
| CVE-2026-21158 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper certificate validation in CP prior to SMR Nov-2026 Release 1 allows local privileged attackers to bypass SIM lock. |
| CVE-2026-21156 | Medium | 2026-11-16 | Not applicable | No public exploit | Out-of-bounds write in libsmkvextractor.so prior to SMR Nov-2026 Release 1 allows local attackers to write out-of-bounds memory. |
| CVE-2026-21155 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Out-of-bounds write in bootloader prior to SMR Nov-2026 Release 1 allows physical attackers to write out-of-bounds memory. |
| CVE-2026-21154 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in libsecuibc.so prior to SMR Nov-2026 Release 1 allows local attackers to access dump data. |
| CVE-2026-21150 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in edmnativehelper prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-21149 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in StatusBarManagerService prior to SMR Nov-2026 Release 1 allows local attackers to use the privileged APIs. |
| CVE-2026-21148 | Medium | 2026-11-16 | Not applicable | No public exploit | Incorrect authorization in Samsung Messages prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-21147 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivity in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21146 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivitySmall in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21145 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper export of android application components in CoverScreenWidgetActionActivityLarge in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21144 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in RecentsCallLogLargeWidgetProvider in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21143 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper authorization in CoverScreenRecentsWidgetProvider in Samsung Contacts prior to SMR Nov-2026 Release 1 allows local attackers to make a call without proper permission. |
| CVE-2026-21141 | Medium | 2026-11-16 | Not applicable | No public exploit | Improper access control in Samsung Dialer prior to SMR Nov-2026 Release 1 allows local attackers to access sensitive information. |
| CVE-2026-18566 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can import EMF, EMF+ and WMF images, which may be embedded in documents. Several out-of-bounds reads existed in the readers for these formats, because sizes, counts and offsets taken from a crafted image were not checked against the data the image actually holds. In fixed versions these values are checked against the size of each record and the data that remains, and a record that fails the checks is not used. |
| CVE-2026-18564 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice can export documents to PDF protected by a password. With the PDF 2.0 option the file is encrypted with 256-bit AES, using a file encryption key and salts that are meant to be random. The key and the salts were drawn from a pseudo-random number generator that is not suitable for cryptography, so the encryption key of an exported PDF could be recovered without knowing the password. In fixed versions the key and the salts are drawn from the random source of the operating system. |
| CVE-2026-18563 | Medium | 2026-11-16 | Not applicable | No public exploit | LibreOffice supports fonts embedded in documents. When a document is exported to PDF, the fonts it uses are embedded in the PDF, and a font in CFF (Compact Font Format) is converted to another font format on the way. An out-of-bounds write existed when the charstring program of a crafted font was interpreted, because some indexes and ranges taken from the font were not checked against the size of the data they refer to. In fixed versions these indexes and ranges are checked, and a font that fails the checks is not converted. |
| CVE-2026-130206 | Medium | 2026-11-16 | Not applicable | No public exploit | Chyrp Lite (xenocrat/chyrp-lite) contains a missing brute-force protection vulnerability in the main_login() function that allows remote attackers to repeatedly submit login attempts against the admin account without any attempt counter, lockout, delay, or CAPTCHA enforcement. Attackers can send unlimited password guesses via POST requests to the login action until a correct credential is found, gaining full administrative control including post publishing, user management, and file uploads. |
| CVE-2026-130083 | Medium | 2026-11-16 | Not applicable | No public exploit | BookStack before 26.09.2 contains an uncontrolled resource consumption vulnerability in the ZIP content importer that allows authenticated users with the Import Content permission to exhaust server storage. Attackers can upload a small ZIP whose data.json references one bundled file many times, causing ZipImportRunner::importAttachment() to write a full copy per reference. |
| CVE-2026-130079 | Medium | 2026-11-16 | Not applicable | No public exploit | B3log Solo through 4.4.0 contains a stored cross-site scripting vulnerability that allows attackers to inject script by setting a malicious article title rendered without escaping. Attackers can set titles, including via the B3 sync endpoint, so admin/article-pwd.ftl, skin templates, and js/page.js article lists execute script in visitors' and administrators' browsers. |
| CVE-2026-130077 | Medium | 2026-11-16 | Not applicable | No public exploit | crw-server before 0.45.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to reach internal hosts via caller-controlled proxy and proxy_list fields in /v1/scrape. Attackers can supply proxy entries pointing to loopback, private-network or link-local hosts, bypassing page URL checks to open HTTP-proxy or SOCKS connections internally. |
| CVE-2026-130076 | Medium | 2026-11-16 | Not applicable | No public exploit | crw-server before 0.45.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to reach internal services by supplying an unvalidated baseUrl to the /v1/scrape endpoint. Attackers can set llmApiKey and request the summary format, making the server POST to loopback or private addresses and use returned warnings as a reachability oracle. |
| CVE-2026-130075 | Medium | 2026-11-16 | Not applicable | No public exploit | SplitPro through 2.1.6 contains a missing authorization vulnerability in the addOrEditExpense and addOrEditCurrencyConversion tRPC mutations that allows authenticated users to assign expenses to arbitrary users. Attackers can enumerate sequential user IDs and supply them in participants or paidBy fields to fabricate debts on victims' balances, even in unseen groups. |
| CVE-2026-130069 | Medium | 2026-11-16 | Not applicable | No public exploit | Frappe Framework before 15.123.0 and 16.x before 16.50.0 contains a server-side request forgery vulnerability in the frappe.email.email_body.get_email_html method, which lacks role checks. Authenticated users, including portal Website Users, can inject stylesheet link tags into unescaped email templates, causing Premailer to fetch internal or external hosts and return the content. |
| CVE-2026-130068 | Medium | 2026-11-16 | Not applicable | No public exploit | Umbraco CMS 17.0.0 before 17.7.1 and 18.0.0 before 18.2.1 contains an authorization bypass vulnerability in Management API document version endpoints that skip per-document ContentPermissionByResource checks. Authenticated back-office users restricted to a start node can list and read document versions outside their tree by GUID, exposing unpublished values and altering prevent-cleanup flags. |
| CVE-2026-130065 | Medium | 2026-11-16 | Not applicable | No public exploit | msgpack-c through 7.0.2 contains a heap buffer overflow vulnerability in msgpack_vrefbuffer_migrate() in src/vrefbuffer.c that checks capacity against the source array's end pointer. When migrating between vrefbuffers of unequal size, the realloc is skipped and memcpy() writes iovec entries past the destination array, corrupting adjacent heap memory or crashing the application. |
| CVE-2026-130064 | Medium | 2026-11-16 | Not applicable | No public exploit | GPAC before 26.07.0 contains a use-after-free vulnerability in gf_sg_command_del() that allows attackers to trigger reads of freed memory through aliased XMT-A SFCommandBuffer command ownership. Attackers can supply a crafted XMT scene file processed by MP4Box, causing commands freed during node destruction to be reaccessed during access unit cleanup, crashing the process. |
| CVE-2026-130063 | Medium | 2026-11-16 | Not applicable | No public exploit | GPAC before 26.07.0 contains a use-after-free vulnerability in the XMT scene loader that allows attackers to read freed heap memory via discarded nodes left on the parser node stack. Attackers can supply a crafted XMT scene file processed by MP4Box, causing xmt_text_content() to call gf_node_get_tag() on a freed node and crash the process. |
| CVE-2026-130062 | Medium | 2026-11-16 | Not applicable | No public exploit | GPAC before 26.07.0 contains a NULL pointer dereference vulnerability in gf_node_get_tag() that allows attackers to crash the process via crafted XMT connect elements. Attackers can supply an XMT scene file whose connect element has a parent with no node, crashing MP4Box during processing and causing denial of service. |
| CVE-2026-130061 | Medium | 2026-11-16 | Not applicable | No public exploit | GPAC before 26.07.0 contains a double free vulnerability in gf_sg_sfcommand_del() that allows attackers to crash the process via crafted XMT scenes. Attackers can supply a crafted XMT/MP4 file where a Conditional node's SFCommandBuffer references a command freed twice during scene teardown, causing MP4Box to crash. |
| CVE-2026-129954 | Medium | 2026-11-16 | Not applicable | No public exploit | NodePress through 8.5.1 contains an HTML injection vulnerability in linesToEmailContent() that allows unauthenticated attackers to inject markup into notification emails because comment content is not escaped. Attackers can post comments or replies via POST /comments containing forged links, images, or tracking resources rendered in administrator and author mail clients from the blog's address. |
| CVE-2026-129953 | Medium | 2026-11-16 | Not applicable | No public exploit | NodePress through 8.5.1 contains a rate limit bypass vulnerability that allows unauthenticated attackers to evade throttling by spoofing the X-Forwarded-For header, because trustProxy is enabled. Attackers can send X-Forwarded-For set to 127.0.0.1 or rotate values to brute-force the administrator password via POST /admin/login and evade comment IP blocklists. |
| CVE-2026-129951 | Medium | 2026-11-16 | Not applicable | No public exploit | Rowy through 3.0.0 contains a stored cross-site scripting vulnerability that allows authenticated users with table write access to inject scripts via URL field links lacking scheme validation. Attackers can store values like javascript: URIs containing the string http in URL cells, executing script when victims click the open-link button to steal Firebase sessions. |
| CVE-2026-129950 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rowy through 3.0.0 contains an incorrect permission assignment vulnerability in default Firebase Storage rules that grants any user holding a role read and write access to the entire bucket. Authenticated users restricted to a single table or read-only access can use the Firebase SDK directly to list, download, overwrite, and delete any stored files. |
| CVE-2026-129949 | Medium | 2026-11-16 | Not applicable | No public exploit | Rowy through 3.0.0 contains a stored cross-site scripting vulnerability that allows authenticated users with table write access to inject unsanitized HTML into Markdown cells. Attackers can store iframe, object, or form elements with javascript: URLs that execute when administrators view the table, stealing Firebase sessions. |
| CVE-2026-129946 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a stored cross-site scripting vulnerability in the DocumentRenderer component that allows authenticated content editors to inject scripts via unvalidated link href values. Editors can paste anchors with javascript: URLs into document fields, executing script when visitors click rendered links and stealing the keystatic-gh-access-token cookie. |
| CVE-2026-129945 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker's GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker's GitHub identity. |
| CVE-2026-129944 | Medium | 2026-11-16 | Not applicable | No public exploit | Keystatic through 0.6.9 contains a path traversal vulnerability in the getIsPathValid function that allows unauthenticated remote attackers to access sibling paths sharing a content directory name prefix. Attackers can send requests with a no-cors header to the blob, update, and tree handlers under /api/keystatic to read, create, overwrite, or delete files such as posts-evil/pwn.yaml. |
| CVE-2026-129942 | Medium | 2026-11-16 | Not applicable | No public exploit | Prime CMS (@primecms/core) through 0.4.0-beta.0 contains a missing authentication vulnerability that allows unauthenticated attackers to invoke privileged GraphQL mutations because the @Authorized() decorator is omitted. Attackers can call updateWebhook, createRelease, unpublishDocument and updateUser at /prime/graphql to create releases and, with a record UUID, redirect webhooks, unpublish documents, or overwrite user profiles. |
| CVE-2026-129940 | Medium | 2026-11-16 | Not applicable | No public exploit | Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an open redirect vulnerability in the unauthenticated GET /prime/redirect route that allows remote attackers to redirect users to external sites. Attackers can craft links with a 36-character id and arbitrary url parameter on the trusted Prime host to send victims to phishing sites. |
| CVE-2026-129887 | Medium | 2026-11-16 | Not applicable | Proof of concept only | thirdweb Dashboard through commit 940b3745 contains an information disclosure vulnerability that allows authenticated users to read non-public team metadata by requesting the team join page with any invite ID. Attackers who know a team slug can obtain the serialized Team object, exposing billing email, billing status, Stripe customer ID, verified domain and support identifiers. |
| CVE-2026-129886 | Medium | 2026-11-16 | Not applicable | Proof of concept only | thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in revalidatePathAction and revalidateCacheTagAction server actions in revalidate.ts. Unauthenticated attackers can use action identifiers exposed in the client bundle to send POST requests that purge cached pages and data, forcing repeated regeneration and degrading performance. |
| CVE-2026-129885 | Medium | 2026-11-16 | Not applicable | No public exploit | Unrolled Secure before 1.18.0 contains an SSLRedirect bypass vulnerability in Secure.isSSL() that trusts the client-supplied r.URL.Scheme to determine HTTPS transport. Attackers can send plaintext HTTP requests with an absolute-form https:// request-target to skip the HTTPS redirect and have application responses served unencrypted. |
| CVE-2026-129884 | Medium | 2026-11-16 | Not applicable | No public exploit | thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in the fetchClientSecret Next.js server action that allows unauthenticated attackers to create Stripe checkout sessions for other teams. Attackers can invoke the action with a forged Team object containing a victim's stripeCustomerId to obtain Growth plan Checkout session client secrets with attacker-influenced return URLs. |
| CVE-2026-129883 | Medium | 2026-11-16 | Not applicable | Proof of concept only | thirdweb Dashboard through commit 940b3745 contains an open redirect vulnerability that allows remote attackers to send users to arbitrary sites by supplying an unvalidated redirectUri parameter on the /pay/[id] payment link page. Attackers can distribute payment links with a malicious redirectUri that PayPageWidget opens via window.open after payment without noopener, enabling phishing and reverse tabnabbing of the payment page. |
| CVE-2026-129882 | Medium | 2026-11-16 | Not applicable | No public exploit | Kiwi TCMS before 17.1 contains a hard-coded cryptographic key vulnerability that allows remote attackers to forge signed data by using the publicly known Django SECRET_KEY in tcms/settings/common.py. Attackers can forge or tamper with signed cookie-based messages and django.core.signing payloads, weakening password-reset and session-authentication HMACs on deployments keeping the default. |
| CVE-2026-129881 | Medium | 2026-11-16 | Not applicable | No public exploit | Weblate 2026.6 through 2026.11.2 contains an information disclosure vulnerability in ChangeManager.last_changes() that exposes workspaces the viewer cannot view by skipping Workspace.can_view() checks site-wide. Anonymous visitors on instances with REQUIRE_LOGIN disabled and only public projects can query /changes/, /api/changes/, or RSS/CSV feeds to obtain hidden workspace names, UUIDs, actions, and timestamps. |
| CVE-2026-129876 | Medium | 2026-11-16 | Not applicable | No public exploit | OfficeCLI 1.0.56 through 1.0.161 contains a stored cross-site scripting vulnerability in the officecli watch preview that allows attackers to inject script via unescaped numbering w:color values. Attackers can craft a DOCX whose color closes the style element, then abuse the unauthenticated /api/batch endpoint to read local files and modify the watched document. |
| CVE-2026-129871 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rocboss paopao-ce through 0.6.0-alpha.3 contains a payment bypass vulnerability that allows unauthenticated attackers to obtain paid attachments by reading storage URLs from the GET /v1/post endpoint. Attackers can download the paid file directly from the unauthenticated LocalOSS /oss static route, whose signed URL expired parameter is never checked. |
| CVE-2026-129869 | Medium | 2026-11-16 | Not applicable | No public exploit | SamWaf 1.0.128 through 1.3.25-beta.11 contains a request body inspection bypass vulnerability in WafEngine.ServeHTTP that skips bodies with chunked encoding or lengths of 2048 bytes or more. Remote unauthenticated attackers can send SQL injection, XSS, command injection, traversal or upload payloads chunked or padded, which reach the protected backend uninspected. |
| CVE-2026-129867 | Medium | 2026-11-16 | Not applicable | Proof of concept only | Rocboss paopao-ce through 0.6.0-alpha.3 contains a stored cross-site scripting vulnerability that allows registered users to inject script by abusing #topic link wrapping in preparePost and parsePostTag. Attackers can publish posts or comments with a crafted topic containing a lone '<' and event handler to steal the PAOPAO_TOKEN JWT from localStorage and take over viewer accounts. |