CVE-2026-92376 is a high-severity vulnerability in TeamViewer Remote Management - Monitoring for Windows prior to version 26.10.1. It involves improper authentication in the inter-process communication mechanism, allowing a local low-privileged authenticated attacker to impersonate the IPC broker. This can lead to arbitrary code execution with SYSTEM privileges, resulting in local privilege escalation.
CVE-2026-92375 is an improper access control vulnerability in the IPC communication between TeamViewer Full Client or Host versions prior to 15.83 and the Remote Management Monitoring component prior to 26.10.1. This flaw allows a local authenticated attacker with low privileges to execute scripts with SYSTEM or root privileges. The vulnerability has a high severity with a CVSS score of 7.8. Fixed versions include 15.83 and 26.10.1 among others.
CVE-2026-92374 is a time-of-check time-of-use (TOCTOU) race condition vulnerability in the privileged helper of TeamViewer Full Client and Host for macOS prior to version 15.83. It involves improper symbolic link handling that allows a local attacker with low privileges to bypass installer package verification and install a malicious package. Exploiting this flaw can lead to local privilege escalation to root.
CVE-2026-92372 is a high-severity out-of-bounds write vulnerability in the screen-image decoder of TeamViewer Full Client for Linux and macOS versions prior to 15.83. It allows remote attackers to execute arbitrary code by supplying crafted screen-image data during a remote-control session or by tricking a user into opening a malicious TeamViewer session recording (.tvs). The flaw arises from missing destination bounds checking, leading to an out-of-bounds write to the image buffer. Exploitation requires user interaction. Fixed versions include 15.83 and certain earlier patch releases for Linux and macOS.
Nodemailer versions from 3.0.0 up to but not including 10.0.13 contain a vulnerability in the SMTP client where certain regular expressions used to detect SMTP AUTH mechanisms cause quadratic backtracking. This leads to a denial of service by blocking the Node.js event loop during the EHLO response parsing if the server returns a crafted response with long whitespace runs and no matching mechanism. The vulnerability can be triggered pre-authentication by an attacker controlling or influencing the SMTP server or man-in-the-middling the connection before STARTTLS. A fix is available in Nodemailer version 10.0.13.
Nodemailer has a vulnerability in its address parser where RFC 5322 comments inside angle-bracket email addresses are not stripped. This causes the comment text and parentheses to be included verbatim in the parsed address, leading to malformed SMTP commands that are rejected by mail servers. The issue affects versions from 3.0.0 up to but not including 10.0.13 and is distinct from previously patched comment handling bugs. A fix is available in version 10.0.13.
Nodemailer SMTP client versions from 3.0.0 up to but not including 10.0.10 contain a vulnerability in the SMTP response parser that allows a malicious or compromised SMTP server to cause a denial of service by sending a large number of continuation lines without a completion line. This triggers quadratic CPU usage in the Node.js event loop, freezing the entire process before authentication occurs. The vulnerability is fixed in version 10.0.10.
An authenticated user with internal_user privileges in LiteLLM can escalate to proxy_admin and execute arbitrary commands on the host. The vulnerability arises because the proxy uses the same encryption key for sealing secrets and minting session tokens, allowing an attacker to forge admin credentials via a crafted API key request. Versions >=1.91.0 and certain earlier versions with EXPERIMENTAL_UI_LOGIN=true are affected. Patches are available in versions 1.100.4, 1.101.3, 1.102.2, 1.103.1, and 1.104.0rc2. Mitigation includes upgrading to a fixed version or disabling EXPERIMENTAL_UI_LOGIN as a temporary workaround.
The msgpack-python C extension has a memory leak vulnerability when deserialization rejects a map key with strict_map_key validation enabled (default). This leak occurs because the decoded map value is not released on key validation failure, causing unbounded memory growth and potential denial of service. Additionally, the streaming Unpacker API may suffer from use-after-free issues due to stale parser-stack references. The issue affects msgpack versions prior to 1.2.3 and has been fixed in 1.2.3.
CVE-2026-117507 is a race condition vulnerability in the a2aproject a2a-java software up to version 1.2.0.Final. It affects the TaskManager.saveTaskEvent function and can be exploited remotely. The issue is resolved by upgrading to version 1.3.0.Final.
The WekaClassifier component in NLTK improperly handles caller-controlled model file paths by passing them directly to the weka Java VM without validating them against NLTK's path security enforcement. This allows an attacker to specify arbitrary file paths for model saving and loading, enabling arbitrary file writes and reads outside the intended data root directories. This vulnerability bypasses the pathsec containment measures introduced in a prior advisory (CVE-2026-81726) and affects NLTK versions prior to 3.10.4.
Authlib versions prior to 1.9.0 contain a critical signature verification bypass vulnerability in the JsonWebSignature.deserialize_json() method. This flaw allows an attacker to submit a JSON Web Signature (JWS) object with an empty signatures array, which the method incorrectly accepts as valid without verifying any signature or requiring a cryptographic key. This leads to a complete authentication bypass where attacker-crafted payloads are accepted as legitimately signed.
A vulnerability in the better-auth deviceAuthorization() plugin versions from 1.3.8-beta.3 up to, but not including, 1.7.0-rc.3 allows an attacker to trick a signed-in user into approving a device login request without showing the requesting client or requested permissions. This can lead to the attacker obtaining a live session token for the user. The issue is fixed starting with version 1.7.0-rc.3.
Pylint versions prior to 4.0.9 use pickle serialization for caching stats in the PYLINT_HOME directory. This allows an attacker with write access to the cache directory to craft malicious pickle files that execute arbitrary code when pylint loads the cache. The vulnerability is fixed in pylint 4.0.9, which stores the cache as JSON instead of pickle. Until upgrading, users should ensure PYLINT_HOME is not set to a shared or group-writable directory.
Satori versions from 0.0.27 up to but not including 0.33.5 improperly escape certain values in generated SVG output, allowing crafted input to be interpreted as SVG markup. This vulnerability can lead to unintended SVG rendering depending on how the SVG is consumed. A fix is available in version 0.33.5. No complete workaround exists other than upgrading; applications that cannot upgrade immediately should avoid rendering attacker-controlled content with Satori.
vLLM versions prior to 0.32.0 contain a resource exhaustion vulnerability in the P2P secondary tier management. An API client can submit many unique peer addresses that never establish connections, causing vLLM to retain sessions and ZeroMQ sockets indefinitely. This leads to exhaustion of the ZeroMQ context socket quota, raising a ZMQError that terminates the EngineCore and shuts down the API server. The vulnerability allows denial of service without requiring privileged access or internal listener connectivity. A fix is available in vLLM 0.32.0.
Rembg versions prior to 2.0.82 have an unauthenticated vulnerability in the /api/remove endpoint that allows attackers to inject malicious SAM models via the extras.sam_model parameter. This enables path traversal and placement of crafted ONNX models that read arbitrary local files and encode their contents into returned PNG images. The flaw allows disclosure of any file accessible by the rembg process, including sensitive files like /etc/passwd. The issue is fixed in version 2.0.82.
Twisted's DNS client UDP transport (twisted.names.dns.DNSDatagramProtocol) accepts DNS responses based solely on matching the 16-bit transaction ID without validating the source address. This allows an attacker able to send UDP packets to the resolver's port to inject forged DNS responses, enabling off-path DNS response spoofing or cache poisoning. The standard client mitigates this risk by using per-query random source ports, increasing entropy, but the missing source address validation remains a security gap. This affects all versions prior to 26.10.0rc1, where the issue is fixed.
CVE-2026-117506 is a medium severity vulnerability in a2aproject a2a-java up to version 1.2.0.Final. It affects the Push Notification Config Store component, specifically the InMemoryPushNotificationConfigStore.setInfo function. The vulnerability allows remote attackers to cause resource consumption through crafted manipulation. Upgrading to version 1.3.0.Final resolves the issue.
CVE-2026-103288 is an authorization bypass vulnerability in the Ghost blogging platform's comment like feature. It allows authenticated members to delete comment likes or dislikes they are not authorized to remove. This issue affects Ghost versions from 5.9.0 up to but not including 6.44.1. The vulnerability is fixed in version 6.44.1.