A flaw was found in ansible-builder. The regular expression used to strip comments from a collection's requirements.txt during introspection is susceptible to super-quadratic backtracking. A requirements file containing a line with a long run of internal whitespace and no comment character causes the comment-stripping routine to consume CPU time proportional to the square of the line length. An attacker who can get a victim to build an execution environment that includes an attacker-supplied collection can cause the ansible-builder build or introspect process to hang, resulting in a denial of service. This issue has no confidentiality or integrity impact.
The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.
With the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['isInstalling'] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files.
Omnispace Agora Project through 26.10.0 contains a stored cross-site scripting vulnerability that allows attackers to inject malicious HTML markup by controlling imported directory data or an uploaded CSV file, as values are rendered into table cell text and value attributes after only Txt::utf8Encode() with no HTML escaping in VuePersonsImportExport.php. Attackers can craft a CSV cell containing an attribute-breakout payload that is rendered verbatim and executed in the browser of the administrator performing the import, leading to arbitrary script execution in the administrative context.
CVE-2026-16305 is a local privilege escalation vulnerability in INFINITT Healthcare System Manager versions 3.0.11.3 through 3.0.11.5. It arises from incorrect permission assignment on a critical resource, specifically a world-writable command manifest file (execlist.txt) processed by SmartUpdate.exe and SmartExecute.exe during application updates. This flaw allows a local attacker with low privileges to execute arbitrary commands with administrator rights.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because an absolute Windows path in namespace_packages.txt is interpreted as an absolute path, bypassing intended directory restrictions. The created __init__.py file contains fixed content and is created with the permissions of the installing process. The issue affects setuptools versions from 1.29.0 up to but not including 1.56.0_1 and is fixed in version 1.56.0_1.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The attacker can influence the destination path of this file, which contains fixed content, but cannot control its contents. This occurs due to improper validation of absolute paths in namespace_packages.txt during the installation process.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's .dist-info/namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. This file is created at a filesystem path influenced by the wheel content, with the permissions of the installing process. The created file has fixed content and the attack requires the target parent directory to pre-exist.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's namespace_packages.txt file to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The created file has fixed content and is placed at a filesystem path influenced by the wheel, with the permissions of the installing process. The issue requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended destination directory. The attacker can control the path where this file is created but not its contents. This occurs because an absolute Windows path in namespace_packages.txt bypasses path checks and leads to file creation at an attacker-influenced location.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The created file has fixed content and is placed at a filesystem path influenced by the wheel, with the permissions of the installing process. The parent directory must already exist for this to occur.
A vulnerability in setuptools on Windows allows a crafted wheel file to cause the installation process to create an __init__.py file outside the intended installation directory. This occurs via attacker-controlled content in the wheel's .dist-info/namespace_packages.txt file, which can specify an absolute Windows path. The created file contains fixed content and is created with the permissions of the installing process. The issue affects legacy wheel installation paths and requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a specially crafted namespace_packages.txt that causes setuptools to create an __init__.py file outside the intended installation directory. This file is created at an attacker-influenced absolute path with fixed content and the permissions of the installing process. The issue arises because the path in namespace_packages.txt is not validated and can be interpreted as an absolute Windows path, leading to directory escape during legacy wheel installation.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The attacker can control the destination path of this file but not its contents. This occurs due to improper validation of absolute paths in namespace_packages.txt during installation. The issue affects setuptools versions >=1.38.0 and <2.30.0_1 and is fixed in version 2.30.0_1.
A vulnerability in setuptools on Windows allows attacker-controlled content in a wheel's namespace_packages.txt file to cause the creation of an __init__.py file outside the intended installation directory during legacy wheel installation. The created file contains fixed content and is placed at a filesystem path influenced by the attacker. The issue requires the target parent directory to pre-exist and occurs due to improper validation of absolute paths in namespace_packages.txt.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel with a malicious .dist-info/namespace_packages.txt file that causes setuptools' legacy wheel installation to create an __init__.py file outside the intended installation directory. This occurs because the namespace package path can be interpreted as an absolute Windows path, bypassing expected directory constraints. The created __init__.py file contains fixed content and is created with the permissions of the installing process. The attack requires the target parent directory to already exist.
A vulnerability in setuptools on Windows allows an attacker to craft a wheel file with a malicious namespace_packages.txt that causes setuptools to create an __init__.py file outside the intended installation directory. This file has fixed content and is created with the permissions of the installing process. The issue arises because an absolute Windows path in namespace_packages.txt is not properly validated and leads to path escape during legacy wheel installation.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The attacker can control the destination path of this file but not its contents. This occurs because an absolute Windows path in namespace_packages.txt is not properly validated and causes path joining to resolve outside the target directory.
A vulnerability in setuptools on Windows allows a crafted wheel's namespace_packages.txt to cause legacy wheel installation to create an __init__.py file outside the intended installation directory. The attacker can control the destination path of this file but not its contents. This occurs because an absolute Windows path in namespace_packages.txt bypasses normal path restrictions during installation.