Improper Authorization Enables Retrieval of Notebook Owner's File Storage Session Token
In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token
In JetBrains Datalore before 2026.4 improper authorisation allowed read the notebook owner's file storage session token
In JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published interactive reports
In JetBrains Datalore before 2026.4 stored XSS in notebook charts was possible via Vega editor link
Xiaomi Mi Browser Android Application (com.mi.globalbrowser) before 14.66.0-gn contains a path traversal vulnerability in the exported ThirdDocViewerActivity component, where CopyExternalFile.copyFromUri() copies content provider streams using an unsanitized filename from the _display_name column without basename reduction or canonical-path checks. A zero-permission co-resident malicious application can supply a crafted content provider with a _display_name containing .. sequences to make the browser write attacker-controlled bytes to an arbitrary path within its external storage directory, escaping the intended cache_docs staging location without requiring user interaction.
In JetBrains Datalore before 2026.4 improper authorisation allowed notebook viewers to modify files
In JetBrains Datalore before 2026.4 hidden notebook code was exposed to unauthenticated users via the public interactive report content endpoint
In JetBrains Datalore before 2026.4 improper owner validation allowed reading another workspace's issues and runs notebook
Heap-based buffer overflow in Remote Desktop Client allows an unauthorized attacker to execute code over a network.
Buffer over-read in Windows Kernel allows an authorized attacker to disclose information locally.
Use after free in Windows Internet Connection Sharing (ICS) allows an authorized attacker to elevate privileges locally.
Exposure of sensitive system information to an unauthorized control sphere in Windows Remote Desktop Services allows an authorized attacker to disclose information over a network.
Heap-based buffer overflow in Windows Storport Miniport Driver allows an unauthorized attacker to elevate privileges with a physical attack.
Use after free in Windows Audio Service allows an authorized attacker to elevate privileges locally.
Use after free in Windows Audio Service allows an authorized attacker to elevate privileges locally.
Improper access control in Windows Win32K allows an authorized attacker to elevate privileges locally.
Numeric truncation error in Windows SMB allows an authorized attacker to execute code over a network.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary SQL commands due to SQL injection.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive information due to improper use of cryptography. The encryption applied to stored data is not implemented with sufficient strength, which weakens its protection.
IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary scripts due to cross-site scripting. Certain URL fields are not sufficiently validated, so malicious script content could run in another user's browser session.
In the Linux kernel, the following vulnerability has been resolved: net/handshake: Take a long-lived file reference at submit handshake_nl_accept_doit() needs the file pointer backing req->hr_sk->sk_socket to survive the window between handshake_req_next() and the subsequent FD_PREPARE() and get_file(). The submit-side sock_hold() does not provide that. sk_refcnt keeps struct sock alive, but struct socket is owned by sock->file: when the consumer fputs the last file reference, sock_release() tears the socket down regardless of any sock_hold. Add an hr_file pointer to struct handshake_req and acquire an explicit reference on sock->file during handshake_req_submit(). handshake_complete() and handshake_req_cancel() release the reference on the completion-bit-winning path. The submit error path must also release the file reference, but after rhashtable insertion a concurrent handshake_req_cancel() can discover the request and race the error path. Gate the error-path cleanup -- sk_destruct restoration, fput, and request destruction -- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same serialization handshake_complete() and handshake_req_cancel() already use. When cancel has already claimed ownership, the submit error path returns without touching the request; socket teardown handles final destruction. The accept-side dereferences are not yet retargeted; that change comes in the next patch.