The hello-bat-fwi9 package on PyPI contains an obfuscated batch (.bat) file that delivers a Remote Access Trojan (RAT) using its own Python runtime and PTH files. The malicious code requires manual activation to execute. This package is part of a known malicious campaign identified as 2026-11-hello-bat-fwi9, continuing a previous campaign named 2026-11-filipt.
GeoNode versions prior to 5.1.0 contain an OS command injection vulnerability (CWE-78) that allows a low-privileged remote user to execute arbitrary operating system commands by uploading a crafted vector file with a malicious layer name. This vulnerability is fixed in GeoNode version 5.1.0.
A critical arbitrary file write vulnerability exists in the Incus (LXD) client when it processes a malicious image server's crafted Incus-Image-Hash header. This flaw allows an attacker to write files to arbitrary locations on the server filesystem, potentially leading to root command execution. The vulnerability arises because the client trusts the Incus-Image-Hash header before validating the downloaded image's SHA-256 hash, enabling directory traversal attacks. A proof-of-concept demonstrates writing to /etc/cron.d to achieve remote code execution. This issue is fixed in version 0.0.0-20260630083100-c5184be310b1.
LXD (Incus) contains a vulnerability in its backup compression algorithm handling that allows argument injection. The software validates only the first token of the user-supplied compression algorithm against an allowlist but does not reject extra arguments. This flaw enables an attacker to inject additional command-line arguments, leading to arbitrary file writes on the host system and potentially arbitrary command execution. A proof-of-concept demonstrates uploading a malicious cron job file via this injection. The vulnerability is rated critical with a CVSS score of 9.9 and has been patched in version 0.0.0-20260630083100-c5184be310b1.
A vulnerability in LXD allows a specially crafted container image with a malicious rootfs symlink to perform arbitrary file read and write operations on the host filesystem. This occurs because the image validation process does not properly handle duplicate top-level rootfs symlinks, enabling root-level access to the host. The flaw can lead to arbitrary command execution on the host system.
A vulnerability in LXD allows a specially crafted container image to read and write arbitrary files on the host system by exploiting a symlink named 'templates' in the image. This can lead to arbitrary command execution on the host. The flaw arises because the tar extraction process does not reject a top-level 'templates' symlink, enabling access to host directories such as /etc/cron.d. A proof of concept demonstrates creating a cron job on the host via this method. The vulnerability is critical with a CVSS score of 9.9 and has been fixed in version 0.0.0-20260203144152-d1c8ba15d160.
LXD contains a vulnerability where the 'exec-output' directory can be a symlink, allowing files to be written to arbitrary locations on the host. This can be exploited to create files such as cron jobs, enabling arbitrary command execution on the host system. The issue arises because top-level symlinks in unpacked images are preserved, and the code follows the symlink when writing output files. A proof-of-concept demonstrates placing a malicious file in /etc/cron.d to achieve code execution.
An improper isolation vulnerability in the Avast sandbox on Windows allows a local, low-privileged attacker running inside the sandbox to access COM interfaces of the Task Scheduler service. This access enables the attacker to escape the sandbox containment and execute code with elevated privileges on the host system. The sandbox virtualizes file system and registry access but does not restrict COM interface access to Task Scheduler, allowing arbitrary code execution outside the sandbox's intended boundaries.
DDEV versions from 1.25.2 up to but not including 1.25.4 contain a path traversal vulnerability in the Untar function of pkg/archive/archive.go. This flaw allows a crafted tar archive to create absolute symlinks that can cause files to be written outside the intended extraction directory. Exploitation can occur through remote add-on retrieval and database or file imports, potentially leading to code execution in the context of the DDEV user. The issue is fixed in version 1.25.4.
CVE-2026-104656 is a cross-site scripting (CWE-79) vulnerability in Progress Telerik Fiddler Everywhere versions before 8.3.0. It allows an attacker to execute backend inter-process communication (IPC) commands by tricking a user into opening a specially crafted SAZ file. This vulnerability was fixed in version 8.3.0.
CVE-2026-80302 is a vulnerability in Gen Digital's Avast Antivirus products that allows a local low-privileged attacker running inside the Avast sandbox on Windows to write arbitrary files outside the sandbox containment. This occurs due to insufficient isolation in the sandbox's file virtualization layer, which improperly validates write targets in some edge cases. Exploiting this flaw can lead to overwriting executable files or system libraries on the host, enabling code execution with host privileges after system operations or reboot.
The Live2DWebCanvas WordPress plugin versions up to and including 2.2.1 contain an arbitrary file upload vulnerability via the download_one_file function. This flaw arises from missing file extension and MIME type validation, allowing unauthenticated attackers to upload potentially executable files. Remote code execution is possible if the plugin is configured with the non-default custom-local apiType setting, which requires a paid license and exposes REST nonce and session tokens on front-end pages.
The ELEX WordPress HelpDesk & Customer Ticketing System plugin up to version 3.3.8 contains a critical vulnerability allowing unauthenticated attackers to delete arbitrary files on the server. This occurs due to insufficient file path validation in the factory_reset function. Exploitation involves a two-step process where an attacker first submits a ticket to set a malicious file path, then triggers the factory reset functionality, which lacks proper capability checks. Deleting sensitive files like wp-config.php can lead to remote code execution.