TeamCity REST API Exposes User Details Not Visible in UI
In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI
Export limit exceeded: 429943 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI
In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox
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
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths
In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings
In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs
In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
Dell PowerStore SDNAS contains a cryptographically weak PRNG vulnerability that could allow a network attacker to decrypt or tamper with NAS SSH/SFTP sessions.
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.
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.
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.
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.
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.
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.
In JetBrains Rider before 2026.3 code execution was possible via MSBuild configuration files in parent directories
In JetBrains ReSharper before 2026.3 server host names were not verified during certificate validation
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.