NLTK versions from 3.10.0 up to but not including 3.10.4 contain a vulnerability where the StreamBackedCorpusView component performs os.stat on a user-supplied file path before enforcing path containment. This can allow an attacker to disclose the existence, size, and modification time of files outside the intended directory, even though file opening is prevented. The issue is fixed in version 3.10.4.
NLTK versions prior to 3.10.4 contain a vulnerability in the SeekableUnicodeStreamReader.readline function where processing an attacker-controlled corpus file with a very long unterminated line causes quadratic CPU consumption. This can lead to denial of service by exhausting CPU resources. The issue is fixed in version 3.10.4.
NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.4, nltk.classify.weka.ARFF_Formatter writes attacker-controlled class labels into the Weka ARFF @ATTRIBUTE '-label-' declaration without safely formatting the label tokens. Crafted labels can alter the generated ARFF schema or records, corrupting classifier input and causing integrity loss or processing failure. This issue is fixed in version 3.10.4.
Joomla Extension - vi-solutions - Missing core.create check in form creation in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The createForm task of the form creator did not check the core.create permission, allowing backend users without create permission to create forms.
NLTK versions prior to 3.10.4 contain an untrusted search path vulnerability in the Prover9Parent.config_prover9 and Mace components. These functions accept a relative binary location and pass it to find_binary without enforcing absolute paths, allowing a local attacker to place malicious binaries named prover9 or mace4 in the working directory. This can lead to execution of these binaries with the invoking user's privileges. The issue is resolved in NLTK version 3.10.4.
Joomla Extension - vi-solutions - Authorization bypass in saveAjaxTextarea task in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The saveAjaxTextarea task did not check edit permissions and accepted arbitrary table and column names, allowing backend users to modify the configuration of any form, including notification recipients.
NLTK versions prior to 3.10.4 contain a vulnerability in the XMLCorpusView.read_block function where processing deeply nested XML corpora causes excessive resource consumption. This leads to quadratic computational work in pure Python, potentially pinning a processing worker and resulting in denial of service. The issue is fixed in version 3.10.4.
Joomla Extension - vi-solutions - Unauthenticated verification mail amplification in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The verification mail task accepted arbitrary form IDs and recipients without rate limiting, allowing unauthenticated attackers to trigger mass verification mails and database entries.
Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The CSS editor did not restrict file names, extensions and paths of created and saved files, allowing privileged backend users to write arbitrary PHP files.
Joomla Extension - vi-solutions - Arbitrary file deletion via path traversal in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The delete and rename tasks of the CSS editor lacked authorization checks, CSRF protection and path validation, allowing backend users to delete files outside the CSS directory.
Joomla Extension - vi-solutions - Open redirect on invalid form submission in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The return parameter of an invalid form submission was not validated, allowing redirects to external sites.
Jupyter MCP Server versions prior to 1.0.3 have a vulnerability where certain management API routes lack proper browser-origin validation. This allows a malicious website to exploit DNS rebinding to manipulate the /api/connect and /api/stop endpoints, potentially redirecting Jupyter API and WebSocket traffic to attacker-controlled infrastructure and stopping notebook kernels. The issue is fixed in version 1.0.3.
Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime_url and document_url values and their tokens, reset ServerContext, and start a kernel client against attacker-controlled infrastructure, causing the server to send Jupyter API and WebSocket traffic to that backend. The caller can also use /api/stop to stop the current notebook kernel. This boundary failure does not require explicit insecure no-auth mode and occurs outside normal MCP JSON-RPC tool dispatch. This issue is fixed in version 1.0.3.
Git LFS versions from 0.6.0 up to but not including 3.8.1 improperly handle line-ending control characters in Git configuration options for submodules. This flaw allows a malicious repository to embed line feed characters in configuration values, potentially causing Git LFS to execute attacker-controlled commands or binaries during fetch or add operations. The vulnerability is fixed in version 3.8.1.
Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential values. Authorization headers are never forwarded to inappropriate hosts and are not the affected secret in this vulnerability. This issue is fixed in version 3.8.1.
Git LFS versions from 1.3.0 up to 3.8.0 contain a vulnerability where crafted option keys in the .lfsconfig file can cause Git LFS to execute arbitrary commands during object fetching. This occurs due to improper filtering of option keys, allowing attackers to mimic configuration options that specify custom transfer commands. The issue is resolved in version 3.8.1.
Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS does not format the SSH URL path component as a single argument when constructing remote object-transfer or authentication commands. Shell metacharacters in the SSH URL can therefore escape the intended path argument and cause arbitrary command execution when the remote Git LFS service passes received commands to a shell without adequate sanitization. Git LFS also incorrectly encodes default HTTPS URLs when an SSH URL is configured and the remote host either does not support Git LFS remote commands over SSH or supports HTTP authentication over SSH but git-lfs-authenticate does not return an explicit HTTP URL. This issue is fixed in version 3.8.1.
Sprout Track versions prior to 1.3.5 use a publicly known hardcoded signing secret if the JWT_SECRET environment variable is not set. This allows unauthenticated attackers on network-reachable deployments to create JWTs with arbitrary claims, including administrative privileges, enabling unauthorized access to sensitive data and administrative functions. The issue is fixed in version 1.3.5. Deployments with a unique JWT_SECRET are not affected, and managed hosted instances have been remediated.
Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3.
A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct an authentication bypass attack due to improper handling of authentication. A successful exploit could allow an attacker to bypass authentication and perform unauthorized actions within the context of the application. This is MTLVULN-1877.