Export limit exceeded: 430018 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 10180 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430018 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430018 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-133014 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.2 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox | ||||
| CVE-2026-133019 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in the Kotlin DSL sandbox | ||||
| CVE-2026-133021 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.5 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths | ||||
| CVE-2026-133025 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.7 High |
| In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings | ||||
| CVE-2026-133028 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.5 Medium |
| In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs | ||||
| CVE-2026-133031 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible | ||||
| CVE-2026-133032 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible | ||||
| CVE-2026-133034 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.4 Medium |
| In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible | ||||
| CVE-2026-111509 | 1 Dell | 15 Powerstore 1000t, Powerstore 1200t, Powerstore 1500 and 12 more | 2026-11-20 | 9.1 Critical |
| Dell PowerStore SDNAS contains a cryptographically weak PRNG vulnerability that could allow a network attacker to decrypt or tamper with NAS SSH/SFTP sessions. | ||||
| CVE-2026-111506 | 1 Dell | 15 Powerstore 1000t, Powerstore 1200t, Powerstore 1500 and 12 more | 2026-11-20 | 8.8 High |
| Dell PowerStore contains a Missing Authentication vulnerability that a network-adjacent attacker could exploit to bypass authentication and authorization, leading to information disclosure and denial of service. | ||||
| CVE-2026-133116 | 2 Termix, Termix-ssh | 2 Termix, Termix | 2026-11-20 | 5.4 Medium |
| Termix 1.7.0 before 26.11.2 contains a path traversal vulnerability that allows authenticated users to write files outside the export directory via crafted usernames. Attackers can self-register with a username containing ../ segments and request POST /database/export to plant attacker-controlled SQLite files in writable directories, enabling disk exhaustion. | ||||
| CVE-2026-133112 | 1 Modified-shop | 2 Modified-shop, Modified Ecommerce Shopsoftware | 2026-11-20 | 3.1 Low |
| modified eCommerce Shopsoftware through 3.3.0 contains a cross-site request forgery vulnerability in gv_send.php because the action=process step never validates a CSRF token via check_secure_form(). Attackers can host an auto-submitting form that makes a logged-in customer send their gift voucher balance to an attacker-controlled email address for redemption. | ||||
| CVE-2026-126086 | 1 Eclipse | 1 Eclipse Dataspace Components | 2026-11-20 | N/A |
| In Eclipse Dataspace Components (EDC) – Connector (`org.eclipse.edc:decentralized-claims-*`, `org.eclipse.edc:jwt-verifiable-credentials`, `org.eclipse.edc:ldp-verifiable-credentials`) there's a credential verification bypass in Decentralized Claims Protocol (DCP) presentation handling: a participant can present credentials appearing to be issued by any trusted issuer without holding them. | ||||
| CVE-2026-133174 | 1 Bufanyun | 1 Hotgo | 2026-11-20 | 4.3 Medium |
| HotGo 2.18.6 through 2.19.0 contains an information disclosure vulnerability that allows authenticated backend users to read other administrators' private letters because the messageIds helper omits the receiver filter. Low-privilege users can call GET /admin/notice/pullMessages, which is exempt from role permission checks via exceptAuth, to retrieve titles, contents and senders of private letters. | ||||
| CVE-2026-133169 | 1 Modified-shop | 2 Modified-shop, Modified Ecommerce Shopsoftware | 2026-11-20 | 4.8 Medium |
| modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the unsanitized products_model field. Attackers with product editing permission can store JavaScript that executes in browsers of other administrators, storefront visitors, and customers viewing carts and order history. | ||||
| CVE-2026-133181 | 1 Jetbrains | 2 Resharper, Rider | 2026-11-20 | 3.7 Low |
| In JetBrains ReSharper before 2026.3 server host names were not verified during certificate validation | ||||
| CVE-2026-99321 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 3.3 Low |
| In the Linux kernel, the following vulnerability has been resolved: rust_binder: wake epoll on self-work queued to poll thread When a thread pushes work to its own todo list, InnerThread::push_work() returns PushWorkRes::OkNotifyPoll if the thread uses epoll, but four call sites in thread.rs discard this return value. As a result, a non-blocking BC_* write that enqueues work onto the calling thread's todo list without also reading will not wake epoll. Check the return value and call self.process.notify_poll(false) when PushWorkRes::OkNotifyPoll is returned. This is similar to commit 97830f3c3088 ("binder: signal epoll threads of self-work"), but in C Binder pending thread work also prevented subsequent process work from waking epoll, causing a permanent hang, which is not the case in Rust Binder. This means that in practice, it merely delays notifications rather than completely failing to send them. | ||||
| CVE-2026-99322 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 6.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays without draining the old channel A completed DurableHandleReqV2 CREATE can be replayed through another channel while its original channel is exiting. The existing replay path returns the open but leaves its connection and oplock references pointing at the old channel. Its open count also stays on that channel, and a later CLOSE through the surviving channel decrements the wrong counter. After checking the owner, lease key and persistent flag, verify that an active open is still published in the requesting session's file table. Do this even when no oplock was granted, and before processing a consumed replay. Do not read a borrowed opinfo session pointer for this check. Keep a healthy original binding. If the original channel is exiting or releasing, move the open and its own oplock references to the requesting channel. Serialize this with CLOSE using the session file-table lock, and with detach, reconnect and notification snapshots using m_lock. The earlier lock index and lease-table changes make their lifetimes independent of this connection change. No old-channel r_count wait is needed, including when an unrelated request remains active there. Account final close against fp->conn in one place, balance durable detach and reconnect, and transfer the count with a replay binding change. A final global lookup put may run after CLOSE has removed the volatile id; unlink the open from the inode list on that final close as well. A live completed CREATE replay may follow a break that lowered the durable open's batch oplock. Apply the batch eligibility check only to detached reconnects, while retaining the owner, lease key and persistent flag checks for active replays. | ||||
| CVE-2026-99323 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 5.3 Medium |
| In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix invalid pointer dereference when get_inode_acl() fails When get_inode_acl() fails, it returns an ERR_PTR(), but ksmbd_acls_fattr() stored that pointer in smb_fattr without checking for errors. Later callers then passed the error pointer to security descriptor helpers or posix_acl_release(), resulting in an invalid pointer dereference. This was reproduced on an XFS-backed share when xfs_get_acl() returned ERR_PTR(-ENOMEM). Querying the SMB ACL from a CIFS client triggered the crash: BUG: unable to handle page fault for address: fffffffffffffff8 RIP: smb_acl_sec_desc_scratch_len+0x58/0x90 [ksmbd] Call Trace: smb2_query_info+0x40d/0x17c0 [ksmbd] handle_ksmbd_work+0x1ca/0x770 [ksmbd] Fix this by checking the return values from get_inode_acl() in ksmbd_acls_fattr(). Treat -EOPNOTSUPP as indicating that no ACL is available, and propagate all other errors to the callers. Update smb2_open() and smb2_get_info_sec() to handle these errors. | ||||
| CVE-2026-99324 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 7.1 High |
| In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out-of-bounds read when padding the final compound response Compound response handling pads the last response of a compound to an 8-byte boundary by growing the final iov and the RFC1002 length. smb2_allocate_rsp_buf() allocates exactly response_sz. A command can fill the response buffer to within 7 bytes of its end, for example a QUERY_INFO whose output is bounded only by the space left. The padding can then run past the allocation, and ksmbd_tcp_writev() reads those bytes when it sends the response. BUG: KASAN: slab-out-of-bounds in _copy_from_iter+0x744/0x10e0 Call Trace: _copy_from_iter+0x744/0x10e0 tcp_sendmsg_locked+0x2290/0x3f80 ksmbd_tcp_writev+0x10c7/0x1ab0 [ksmbd] Allocate room for the padding when the request is a compound, as smb2_read() and smb2_read_pipe() do for their payloads. response_sz is unchanged, so commands still fill only up to it, and kvzalloc() zeroes the padding. | ||||