CVE-2026-19827 in alldata
Summary
by MITRE • 08/14/2026
A flaw has been found in alldatacenter alldata up to 0.6.8. This impacts the function FileInputStream of the file /admin/controller/JobLogController.java of the component logDetailCat Endpoint. This manipulation of the argument executorAddress causes path traversal. It is possible to initiate the attack remotely. The exploit has been published and may be used. The project closed the issue report as "not planned" without any further explanation.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 08/14/2026
The vulnerability identified in alldatacenter alldata up to version 0.6.8 represents a critical path traversal flaw within the logDetailCat endpoint of the JobLogController.java component. This security weakness resides in the FileInputStream function where the executorAddress argument is improperly handled, allowing attackers to manipulate file paths and potentially access unauthorized system resources. The vulnerability specifically affects the administrative interface component that manages job log details, creating a significant attack surface for malicious actors seeking to exploit the system's file handling mechanisms.
The technical implementation of this flaw stems from inadequate input validation and sanitization of the executorAddress parameter within the FileInputStream method. When this parameter is processed without proper boundary checks or path normalization, it enables attackers to craft malicious input that traverses directory structures beyond the intended scope. This type of vulnerability maps directly to CWE-22 Path Traversal and falls under the ATT&CK technique T1059 Command and Scripting Interpreter, where adversaries manipulate system components to execute unauthorized operations. The remote exploitability aspect means that attackers do not require physical access to the system but can leverage network-based attacks to compromise the application.
The operational impact of this vulnerability extends beyond simple data access, as successful exploitation could enable attackers to read sensitive files, potentially including configuration data, authentication credentials, or other system-related information. The fact that a working exploit has been published indicates that this vulnerability is not theoretical but actively being used in the wild, making it particularly dangerous for organizations running affected versions. The project's decision to close the issue report as "not planned" without explanation suggests either a lack of understanding of the severity or an unwillingness to address the vulnerability, leaving users exposed to potential compromise.
Organizations utilizing this software should immediately implement mitigations including input validation at all entry points, implementation of proper path normalization techniques, and restriction of file access permissions. The recommended approach involves sanitizing all user-supplied parameters before processing, implementing whitelisting mechanisms for valid paths, and employing principle of least privilege access controls for the logDetailCat endpoint. Additionally, network-level protections such as web application firewalls should be configured to monitor and block suspicious path traversal patterns. Given the published exploit availability, proactive remediation is essential rather than reactive response measures.