NVIDIA TensorRT-LLM has a vulnerability identified as CVE-2026-65120 that allows an attacker to perform server-side request forgery (SSRF). Exploitation of this vulnerability could lead to information disclosure. The vulnerability has a high severity rating with a CVSS score of 7.1. No affected versions or patch information are currently provided.
LiteLLM versions prior to 1.95.0 contain a vulnerability allowing an authenticated user with internal_user_viewer privileges to read arbitrary local files via a crafted vertex_ai_credentials value. This occurs because the request-body safety blocklist missed the alias vertex_ai_credentials, enabling file read access that can disclose sensitive environment variables and escalate privileges. The issue is fixed in version 1.95.0.
A concurrency issue in @better-auth/drizzle-adapter and @better-auth/kysely-adapter when using PostgreSQL for rate-limit record storage can allow bursts of concurrent requests to exceed configured rate limits. This affects versions 1.6.17 up to but not including 1.7.7 for drizzle-adapter and up to but not including 1.7.0 for kysely-adapter. The flaw weakens rate limiting on sensitive endpoints like password sign-in and two-factor verification but does not bypass authentication or directly compromise accounts.
A vulnerability in better-auth versions from 1.5.0-beta.12 up to but not including 1.7.7 with the OAuth Proxy plugin allows an attacker to sign in as another user if certain conditions are met. The issue arises when the OAuth Proxy plugin shares the same secret as the global Better Auth secret, sign-in state is stored in a cookie, and implicit account linking is enabled. An attacker who knows a user's verified email can impersonate that user without needing provider sign-in or victim interaction. The flaw is fixed in version 1.7.7.
A critical vulnerability in better-auth versions from 1.4.0-beta.18 up to but not including 1.7.7 allows an unauthenticated attacker to use the OAuth state value as a Magic Link token to sign in as any user by knowing only their email address. This bypasses email verification and OAuth provider authentication, granting full session access. The flaw affects configurations using Magic Link with default or hashed token storage combined with social or Generic OAuth sign-in and database-backed OAuth state storage. The issue is fixed in version 1.7.7.
LiteLLM versions from 1.65.5 up to but not including 1.85.0 contain a reflected cross-site scripting (XSS) vulnerability in the /sso/debug/callback endpoint. This endpoint reflects identity-provider-controlled fields into an inline script block without properly escaping HTML context characters, allowing an attacker to inject malicious JavaScript. The vulnerability can be exploited by an attacker with an account on the configured identity provider to execute scripts in the proxy origin, potentially leading to full admin account takeover.
CVE-2026-117509 is a path traversal vulnerability in the crownpku Rasa_NLU_Chi project affecting versions 0.12.0, 0.12.1, and 0.12.2. The flaw exists in the Persistor._decompress function within the rasa_nlu/persistor.py file. This vulnerability allows remote attackers to manipulate file paths, potentially accessing unauthorized files. Public exploit code is available, but no official vendor response or patch has been issued yet.
GitPython versions up to 3.1.62 contain a vulnerability in the Head.checkout() method that allows an attacker to cause an arbitrary file read via a specially crafted branch name. The flaw arises because the positional branch name argument is not properly sanitized and is passed directly to the git checkout command without a separator, enabling injection of options such as --pathspec-from-file to read files like /etc/passwd. This issue is an incomplete fix of previous advisories and affects all published releases up to 3.1.62. A fix is available in version 3.2.0.
GitPython's Submodule.move() API does not properly handle symbolic links in intermediate path components, allowing an attacker controlling a Git repository with a symlinked submodule path to cause the submodule to be moved outside the parent repository's worktree. This leads to an integrity violation where repository content is relocated to an attacker-chosen directory outside the expected location, corrupting the parent repository's index and configuration. The issue affects GitPython versions prior to 3.2.0 and requires the application to explicitly call Submodule.move() on a path under the symlink. No code execution or confidentiality impact is demonstrated.
GitPython's Remote.pull() method improperly handles the positional refspec argument, allowing an attacker to inject a --upload-pack option that bypasses the unsafe-option guard. This leads to arbitrary command execution with the privileges of the calling process when using local-path or SSH transports. The vulnerability is fixed in version 3.2.0.
GitPython versions prior to 3.2.0 have security weaknesses in three command wrapper methods—ls_remote, merge_base, and IndexFile.move—that omit checks for unsafe protocols and options. This omission allows potential command injection or remote code execution (RCE) when interacting with maliciously crafted git URLs or arguments, particularly if the underlying git transport policy permits unsafe protocols like 'ext'. The vulnerability is confirmed on the main branch as of 2026-09-21 and affects versions before 3.2.0. A fix is available in version 3.2.0.
GitPython versions prior to 3.2.0 have a vulnerability in the handling of the separate_git_dir parameter during repository cloning. This flaw allows environment variable expansion from attacker-controlled .gitmodules submodule names, leading to leakage of environment variable values. The expanded values are exposed persistently on disk as directory names and in debug-level logs, potentially disclosing sensitive environment variables.
GitPython versions prior to 3.2.0 contain a vulnerability in the parse_actor_and_date() function due to a regex pattern that causes quadratic backtracking on malformed author, committer, or tagger identity lines. This results in CPU exhaustion when processing crafted commit or tag objects with malformed identity lines lacking valid epoch or timezone information. The issue was fixed in version 3.2.0 by modifying the regex to prevent overlapping matches and eliminate the backtracking.
Tailscale SSH suffers from multiple privilege escalation vulnerabilities collectively called 'Tailworm,' disclosed publicly before patches were available. These flaws allow an attacker with access to a compromised device to escalate privileges on any server reachable via Tailscale SSH, potentially gaining root access and stealing keys to add rogue devices. The vulnerabilities enable wormable attacks that can propagate rapidly across servers without user interaction. Tailscale is preparing patches, with fixes already committed to public repositories but not yet released in a numbered version. Until patched, disabling SSH forwarding where not needed mitigates several serious issues.
CVE-2026-104189 is a vulnerability in the maz1987in 3Dviewer-Nextcloud app versions 1.7.9 through 3.3.1 where the public file endpoint did not enforce share authorization properly. This allowed anyone with a share token to access password-protected 3D model files without providing the password. The issue was fixed in version 3.3.2 by improving token and password validation and adding brute-force throttling.
CVE-2026-111585 is an integer overflow vulnerability in the remote-control screen processing component of TeamViewer Full Client, Portable, and Remote Control App versions prior to 15.83. A malicious remote host could exploit this flaw to cause denial of service or potentially execute arbitrary code with the privileges of the viewer process. Exploitation requires a user to initiate a remote-control session to an attacker-controlled or compromised host. The vulnerability has a high severity with a CVSS score of 8.8 and has been fixed in version 15.83 and several legacy versions.
A race condition vulnerability in the installation process of TeamViewer Remote Management - Patch Management for Windows versions prior to 26.9.1 allows a local authenticated user with low privileges to execute arbitrary code with elevated privileges by replacing the service executable in a temporary directory during activation.
CVE-2026-111583 is a high-severity vulnerability in TeamViewer Full Client and Host for Windows prior to version 15.82. It involves improper access control in the installer staging directory during the installation of Advanced Asset Management. This flaw allows a local authenticated user with low privileges to execute arbitrary commands with SYSTEM-level privileges by placing a crafted installer options file processed during service activation.
CVE-2026-111582 is a DLL loading vulnerability in the TeamViewer Remote Management Monitoring installer for Windows versions prior to 26.10.1. It allows a local authenticated user with low privileges to execute arbitrary code with elevated privileges. Exploitation requires user interaction. The vulnerability is fixed in version 26.10.1.
CVE-2026-92377 is a high-severity vulnerability in TeamViewer Full Client and Host for Windows prior to version 15.82. It involves improper access control in the Patch Management update mechanism, allowing a local authenticated attacker with low privileges to execute arbitrary code with SYSTEM privileges by supplying a signed executable through a forged IPC response. The issue is fixed in versions 15.82, 15.64.10 (Legacy Windows 7 & 8), 14.7.48868, and 13.2.36231.