A NULL pointer dereference vulnerability in the Linux kernel's USB Target driver (f_tcm) was fixed. The issue arises when the tpg->tpg_nexus pointer is NULL during certain USB Bulk-Only Transport (BOT) commands, causing kernel panic and local denial of service. The fix adds missing NULL checks to prevent crashes by aborting commands gracefully.
Akamai Guardicore Platform Agent (GPA) and Zero Trust Client on Linux and macOS allow TOCTOU-based local privilege escalation. The GPA service creates an IPC socket in the world-writable /tmp directory. It accepts unauthenticated IPC control messages. This enables a TOCTOU vulnerability in the HandleSaveLogs() function of the GPA service, by creating a log file and manipulating it into a symlink that points to the targeted path; this can allow an unprivileged local user to make arbitrary root-owned files world-writable. In addition, a diagnostic collection tool (gimmelogs) running with root privileges was vulnerable to command injection from the dbstore, offering a second privilege escalation vector. (On Windows, gimmelogs does not have command injection but does allow writing a ZIP archive to an unintended location.) This affects Akamai Guardicore Platform Agent 7.0 through 7.3.1 and Akamai Zero Trust Client 6.0 through 6.1.5.
mcp-ssh-tool versions prior to 2.1.1 contain security weaknesses in transfer path policy enforcement and HTTP bearer token comparison. These issues allow bypassing local path restrictions during file transfers and expose a timing side channel in token validation. Version 2.1.1 includes fixes that strengthen path authorization and implement constant-time token comparison to mitigate these risks.
CVE-2026-44407 is a medium severity vulnerability in the ZTE ZXCLOUD iRAI client (version 7.2X) involving an externally-controlled format string issue (CWE-134). This flaw can cause memory corruption leading to a remote denial-of-service condition. The vulnerability requires local access with low privileges and high attack complexity, with no user interaction needed. No official patch or remediation guidance has been provided by the vendor at this time, and no known exploits are reported in the wild.
This security update for java-11-openjdk addresses multiple vulnerabilities that allow unauthenticated attackers with network or local logon access to gain unauthorized read access to data or cause partial denial of service conditions. The update upgrades to upstream tag jdk-11.0.31+11 (April 2026 CPU) and includes fixes for several CVEs affecting components such as JGSS, JAXP, JSSE, freetype2, and networking. Additionally, other bug fixes and timezone data updates are included.
CVE-2026-7997 is a vulnerability in Google Chrome on Mac systems prior to version 148.0.7778.96. It involves insufficient validation of untrusted input in the Chrome Updater component, which allows a local attacker to escalate privileges to the operating system level by leveraging a malicious file. The vulnerability has a high severity rating with a CVSS score of 7.8. There are no known exploits in the wild at this time. The vendor advisory linked does not explicitly confirm patch availability or remediation status.
CVE-2026-7994 is a high-severity vulnerability in Google Chrome on Windows prior to version 148.0.7778.96. It involves an inappropriate implementation in the Chromoting component that allows a local attacker to escalate privileges to the operating system level by using a malicious file. The vulnerability has a CVSS score of 7.8, indicating significant impact on confidentiality, integrity, and availability. There are no known exploits in the wild at this time. The vendor advisory linked does not explicitly confirm patch availability or remediation status.
CVE-2026-7990 is a vulnerability in Google Chrome on Windows prior to version 148.0.7778.96 involving insufficient validation of untrusted input in the Updater component. This flaw allows a local attacker to escalate privileges to the operating system level by leveraging a malicious file. The vulnerability has a high severity rating with a CVSS score of 7.8. There are no known exploits in the wild at this time. The vendor has published an advisory but has not explicitly stated the availability of a patch or remediation level in the provided data.
CVE-2026-7948 is a race condition vulnerability in the Chromoting component of Google Chrome on Windows versions prior to 148.0.7778.96. This flaw allows a local attacker to escalate privileges by leveraging a malicious file. The vulnerability has a CVSS score of 7.5, indicating high severity. There are no known exploits in the wild at this time. The vendor has published an advisory linked to a stable channel update, but explicit patch status is not confirmed in the provided data.
CVE-2026-7925 is a use-after-free vulnerability in the Chromoting component of Google Chrome on Windows versions prior to 148.0.7778.96. This flaw allows a local attacker to escalate privileges to the operating system level by leveraging a malicious file. The vulnerability has a high severity rating and a CVSS score of 7.8. There are no known exploits in the wild at this time. Google has published an advisory indicating a stable channel update addressing this issue.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Refactor amdgpu_gem_va_ioctl for Handling Last Fence Update and Timeline Management v4 This commit simplifies the amdgpu_gem_va_ioctl function, key updates include: - Moved the logic for managing the last update fence directly into amdgpu_gem_va_update_vm. - Introduced checks for the timeline point to enable conditional replacement or addition of fences. v2: Addressed review comments from Christian. v3: Updated comments (Christian). v4: The previous version selected the fence too early and did not manage its reference correctly, which could lead to stale or freed fences being used. This resulted in refcount underflows and could crash when updating GPU timelines. The fence is now chosen only after the VA mapping work is completed, and its reference is taken safely. After exporting it to the VM timeline syncobj, the driver always drops its local fence reference, ensuring balanced refcounting and avoiding use-after-free on dma_fence. Crash signature: [ 205.828135] refcount_t: underflow; use-after-free. [ 205.832963] WARNING: CPU: 30 PID: 7274 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 ... [ 206.074014] Call Trace: [ 206.076488] <TASK> [ 206.078608] amdgpu_gem_va_ioctl+0x6ea/0x740 [amdgpu] [ 206.084040] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.089994] drm_ioctl_kernel+0x86/0xe0 [drm] [ 206.094415] drm_ioctl+0x26e/0x520 [drm] [ 206.098424] ? __pfx_amdgpu_gem_va_ioctl+0x10/0x10 [amdgpu] [ 206.104402] amdgpu_drm_ioctl+0x4b/0x80 [amdgpu] [ 206.109387] __x64_sys_ioctl+0x96/0xe0 [ 206.113156] do_syscall_64+0x66/0x2d0 ... [ 206.553351] BUG: unable to handle page fault for address: ffffffffc0dfde90 ... [ 206.553378] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.553405] Call Trace: [ 206.553409] <IRQ> [ 206.553415] ? __pfx_drm_sched_fence_free_rcu+0x10/0x10 [gpu_sched] [ 206.553424] dma_fence_signal+0x30/0x60 [ 206.553427] drm_sched_job_done.isra.0+0x123/0x150 [gpu_sched] [ 206.553434] dma_fence_signal_timestamp_locked+0x6e/0xe0 [ 206.553437] dma_fence_signal+0x30/0x60 [ 206.553441] amdgpu_fence_process+0xd8/0x150 [amdgpu] [ 206.553854] sdma_v4_0_process_trap_irq+0x97/0xb0 [amdgpu] [ 206.554353] edac_mce_amd(E) ee1004(E) [ 206.554270] amdgpu_irq_dispatch+0x150/0x230 [amdgpu] [ 206.554702] amdgpu_ih_process+0x6a/0x180 [amdgpu] [ 206.555101] amdgpu_irq_handler+0x23/0x60 [amdgpu] [ 206.555500] __handle_irq_event_percpu+0x4a/0x1c0 [ 206.555506] handle_irq_event+0x38/0x80 [ 206.555509] handle_edge_irq+0x92/0x1e0 [ 206.555513] __common_interrupt+0x3e/0xb0 [ 206.555519] common_interrupt+0x80/0xa0 [ 206.555525] </IRQ> [ 206.555527] <TASK> ... [ 206.555650] RIP: 0010:dma_fence_signal_timestamp_locked+0x39/0xe0 ... [ 206.555667] Kernel panic - not syncing: Fatal exception in interrupt
CVE-2026-43100 is a vulnerability in the Linux kernel bridge component where local VLAN-0 FDB helper functions dereference a NULL vlan group pointer when VLAN filtering is disabled. This can cause a kernel crash (general protection fault) due to null pointer dereference during bridge configuration changes involving specific boolean options. The issue affects multiple Linux kernel versions and has been fixed in version 7.0.0-1006.6.
The backend for Jupyter web applications
Security Fix(es):
Jupyter Server is the backend for Jupyter web applications. In jupyter_server versions through 2.17.0, the next query parameter in the login flow is insufficiently validated in `LoginFormHandler._redirect_safe()`, which allows redirects to arbitrary external domains via values such as `///example.com`. An attacker can use a crafted login URL to redirect users to a malicious site and facilitate phishing attacks. This issue is fixed in version 2.18.0.(CVE-2025-61669)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named "test", the API permits access to a sibling directory named "testtest" through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named "user1" could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.
Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.(CVE-2026-35397)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the Origin header validation uses Python's re.match() to check incoming origins against the allow_origin_pat configuration value. Because re.match() only anchors at the start of the string and does not require a full match, a pattern intended to match only a trusted domain (e.g., trusted.example.com) will also match any origin that begins with that domain followed by additional characters (e.g., trusted.example.com.evil.com). An attacker who controls such a domain can bypass the CORS origin restriction and make cross-origin requests to the Jupyter Server API from an untrusted site. This issue has been fixed in version 2.18.0.(CVE-2026-40110)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the secret used to sign authentication cookies is persisted to a static file at ~/.local/share/jupyter/runtime/jupyter_cookie_secret and is never rotated when a user changes their password. After a password reset and server restart, any previously issued authentication cookie remains cryptographically valid because the signing key has not changed. An attacker who has captured a session cookie through any means retains full authenticated access to the server regardless of subsequent password changes. This affects deployments using password-based authentication, particularly shared or public-facing servers where credential rotation is expected to revoke existing sessions. This issue has been fixed in version 2.18.0.(CVE-2026-40934)
A vulnerability has been found in chatchat-space Langchain-Chatchat up to 0.3.1.3. Impacted is the function files of the file libs/chatchat-server/chatchat/server/api_server/openai_routes.py of the component OpenAI-Compatible File Upload API. Such manipulation of the argument file.filename leads to time-of-check time-of-use. Access to the local network is required for this attack to succeed. The attack requires a high level of complexity. The exploitability is considered difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-20447 is an out-of-bounds read vulnerability (CWE-125) in MediaTek chipsets affecting multiple models. It exists in the geniezone component due to a missing bounds check, potentially allowing a local escalation of privilege if the attacker already has System privileges. No user interaction is required for exploitation. The vulnerability has a CVSS score of 6.7, indicating medium severity. There is no confirmed patch or official remediation available at this time, and no known exploits in the wild have been reported.
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix stale direct dispatch state in ddsp_dsq_id @p->scx.ddsp_dsq_id can be left set (non-SCX_DSQ_INVALID) triggering a spurious warning in mark_direct_dispatch() when the next wakeup's ops.select_cpu() calls scx_bpf_dsq_insert(), such as: WARNING: kernel/sched/ext.c:1273 at scx_dsq_insert_commit+0xcd/0x140 The root cause is that ddsp_dsq_id was only cleared in dispatch_enqueue(), which is not reached in all paths that consume or cancel a direct dispatch verdict. Fix it by clearing it at the right places: - direct_dispatch(): cache the direct dispatch state in local variables and clear it before dispatch_enqueue() on the synchronous path. For the deferred path, the direct dispatch state must remain set until process_ddsp_deferred_locals() consumes them. - process_ddsp_deferred_locals(): cache the dispatch state in local variables and clear it before calling dispatch_to_local_dsq(), which may migrate the task to another rq. - do_enqueue_task(): clear the dispatch state on the enqueue path (local/global/bypass fallbacks), where the direct dispatch verdict is ignored. - dequeue_task_scx(): clear the dispatch state after dispatch_dequeue() to handle both the deferred dispatch cancellation and the holding_cpu race, covering all cases where a pending direct dispatch is cancelled. - scx_disable_task(): clear the direct dispatch state when transitioning a task out of the current scheduler. Waking tasks may have had the direct dispatch state set by the outgoing scheduler's ops.select_cpu() and then been queued on a wake_list via ttwu_queue_wakelist(), when SCX_OPS_ALLOW_QUEUED_WAKEUP is set. Such tasks are not on the runqueue and are not iterated by scx_bypass(), so their direct dispatch state won't be cleared. Without this clear, any subsequent SCX scheduler that tries to direct dispatch the task will trigger the WARN_ON_ONCE() in mark_direct_dispatch().
A vulnerability in the Linux kernel's Bluetooth management subsystem was resolved by validating the Long Term Key (LTK) encryption size on load. The flaw allowed an oversized encryption size value to overflow a fixed-size stack buffer when replying to LE LTK requests. This could lead to memory corruption. The issue affects specific Linux kernel versions and has been patched. The vulnerability has a CVSS score of 7.8, indicating high impact on confidentiality, integrity, and availability, but requires local privileges and low attack complexity.
A code injection vulnerability exists in ExifTool up to version 13.53 affecting the Process_mrld function in the JPEG/QuickTime/MOV/MP4 component. The vulnerability is triggered by manipulation of the -ee argument and requires local access to exploit. Upgrading to version 13.54 addresses this issue.
The popular PyPI package lightning experienced a supply chain attack affecting versions 2.6.2 and 2.6.3, published on April 30, 2026. The compromise introduced malicious code that executes automatically upon module import, downloading Bun JavaScript runtime and executing an 11MB obfuscated payload. The attack harvests credentials including GitHub tokens, npm tokens, cloud credentials from AWS, Azure, and Google Cloud, while targeting CI/CD environments. The malicious code poisons GitHub repositories by injecting backdoored files impersonating Claude Code commits and infects local npm packages through tarball manipulation. The attack shows similarities to previous Shai-Hulud campaigns in terms of credential targeting and obfuscation methods. Evidence suggests the maintainer's GitHub account (pl-ghost) was compromised, with suspicious branch operations and disclosure suppression indicating ongoing attacker control. The incident affects a widely-used deep learning framework receiving millions of monthly downl...