LMS (Lan Management System) is vulnerable to Remote Code Execution via unrestricted upload of dangerous file types in the service ticket feature of the client panel. The application does not verify the type or name of files attached to service tickets. An authenticated attacker can upload an .htaccess file to bypass the access restrictions on the storage directory, together with a PHP script. Visiting the uploaded PHP file's URL leads to arbitrary code execution with the privileges of the web server.
This issue was fixed in commit 89dd3f7.
paicoding 1.0.0 through 1.0.3 contains a stored cross-site scripting vulnerability in image upload because ImageServiceImpl.validateStaticImg accepts SVG files, which are then served from the site origin when local storage is used. Authenticated attackers can upload script-bearing SVG images that execute when victims view them, stealing the non-HttpOnly f-session cookie to hijack accounts.
NocoDB before 2026.06.2 contains an attachment size limit bypass that allows authenticated Editor users to store oversized files because data-attachment-v3.service.ts trusts the remote server's advertised content length. Attackers can point the v3 upload-by-URL endpoint at a server that understates or omits its length to exhaust disk space or storage quota.
A critical vulnerability in Active Storage's image analysis using ImageMagick allows unauthenticated attackers to write arbitrary files on the server and read sensitive files when using the Disk service. This can expose secrets such as secret_key_base and credentials, potentially leading to remote code execution or lateral movement. The issue arises because ImageMagick's coders are not constrained, enabling crafted files to invoke dangerous coders. Fixed versions introduce a security policy restricting risky coders and delegates.
A denial-of-service (DoS) vulnerability exists in Action Pack's Action Controller Live streaming feature due to improper handling of the response buffer's end-of-stream marker. When the client stops reading and the response queue is full, pushing the end-of-stream marker blocks and causes threads to wait indefinitely, potentially exhausting server threads. This affects applications using ActionController::Live streaming, including send_stream and Active Storage proxy mode for large files. Fixed versions 8.1.4.1 and 8.0.5.2 address this issue.
A vulnerability in BusyBox's volume identification component causes a divide-by-zero error when processing specially crafted FAT filesystems. This leads to a denial-of-service (DoS) condition by crashing probing utilities, potentially disrupting device discovery and system boot operations. The issue requires local access or the ability to introduce crafted storage media. It primarily affects recovery environments or minimal container images using BusyBox for storage probing. No fix is currently available, and mitigation options are limited.
CVE-2026-123747 is a directory traversal vulnerability in the OpenPrinting pappl-retrofit application. It occurs because the application does not properly sanitize user-supplied filenames when uploading or deleting PostScript Printer Description (PPD) files. An unauthenticated remote attacker with elevated privileges can exploit this flaw to upload or delete arbitrary files on the system, potentially causing data corruption, denial of service, or arbitrary command execution. Default installations are not vulnerable unless the required storage directory is manually created with administrative privileges and the service is actively running.
CVE-2026-124746 is an integer overflow vulnerability in the volume_id component of BusyBox used in Red Hat Hardened Images. The flaw occurs when calculating buffer boundaries while probing filesystem metadata, leading to a crash of utilities like blkid, findfs, or mount when processing a specially crafted filesystem image on attached storage. This results in a denial of service (DoS) that prevents the system from resolving or mounting storage devices. The vulnerability primarily affects minimal environments, rescue shells, or specialized containers using BusyBox for filesystem probing, as standard Red Hat Enterprise Linux uses util-linux instead. No fix or mitigation meeting Red Hat's criteria is currently available.
CVE-2026-124743 is a vulnerability in BusyBox affecting the volume identification component when processing HFS+ filesystem metadata. Improper validation of header values can lead to a divide-by-zero error, causing an application crash and resulting in a local denial of service (DoS). Exploitation requires local access to attach a specially crafted storage device or filesystem image. The impact is limited to DoS without confidentiality or integrity loss. BusyBox is typically used in rescue or initramfs environments in Red Hat Enterprise Linux, reducing exposure since standard tools do not rely on it for filesystem resolution. No fix or mitigation currently meets Red Hat's criteria for deployment and stability.
A divide-by-zero vulnerability exists in the volume identification component of BusyBox used in Red Hat Hardened Images. This flaw occurs when specially crafted FAT filesystem parameters cause partition scanning utilities to crash, resulting in a denial of service that can disrupt device discovery and system boot operations. The vulnerability requires local access or the ability to introduce a crafted storage device. It primarily affects recovery environments or minimal container images using BusyBox rather than standard Red Hat Enterprise Linux installations. No mitigation is currently available that meets Red Hat's criteria, but an updated BusyBox package addressing this issue has been released.
A vulnerability in Rails Active Storage prior to 8.0.5.2 and from 8.1 until 8.1.4.1 allows attackers to cause FFmpeg to open local media files readable by the application process. This occurs because Active Storage's video and audio previewers and analyzers pass uploaded blob contents to FFmpeg without restricting the demuxer, enabling an attacker to craft uploads that trigger the hls demuxer and access local file:// segments. The issue is fixed in versions 8.0.5.2 and 8.1.4.1.