CVE-2026-114040 in BerryNet
Summary
by MITRE • 10/22/2026
A security vulnerability has been detected in DT42 BerryNet up to 3.10.2. The affected element is the function DLModelManager.get_model_meta of the file berrynet/dlmodelmgr.py of the component Model Package Metadata Handler. The manipulation of the argument label leads to path traversal. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 10/22/2026
The DT42 BerryNet platform, specifically versions up to 3.10.2, contains a critical security vulnerability within its Deep Learning Model Package Metadata Handler component. This flaw resides in the DLModelManager.get_model_meta function located in the berrynet/dlmodelmgr.py file. The core issue is a path traversal vulnerability triggered by improper validation of user-supplied input, specifically the label argument passed to this function. When an attacker provides a maliciously crafted string containing directory traversal sequences such as dot-dot-slash or encoded equivalents, the application fails to sanitize these inputs before using them in file system operations. This lack of rigorous input sanitization allows the application to resolve paths outside of its intended secure directory structure, effectively breaking out of the sandboxed environment designed for model storage and retrieval.
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which highlights the failure to restrict file access to authorized directories. From an offensive security perspective, this aligns with ATT&CK technique T1083: File and Directory Discovery, as it enables an attacker to enumerate and potentially read sensitive files on the underlying host system. The operational impact of exploiting this flaw is severe because it can lead to unauthorized data disclosure or information leakage. An attacker could use this path traversal to access configuration files containing API keys, database credentials, or other secrets stored within the BerryNet environment. In more complex scenarios involving specific file types and server configurations, such vulnerabilities can sometimes be chained with other flaws to achieve remote code execution, although in this instance, the primary risk is information disclosure through arbitrary file read capabilities.
The severity of this vulnerability is compounded by its exploitable nature over a network connection. The attack vector is classified as Remote (Network), meaning that an unauthenticated or authenticated attacker can exploit this flaw without physical access to the device. Furthermore, the fact that the exploit has been disclosed publicly significantly increases the risk landscape. Publicly available exploits lower the barrier to entry for malicious actors who may lack sophisticated development skills but possess automated scanning tools capable of detecting and leveraging known vulnerabilities. This situation creates a high probability of opportunistic attacks against deployed BerryNet instances that have not yet applied mitigations or updated their software versions.
Although the project maintainers were notified early through an issue report, they have not yet responded with a patch or official acknowledgment. In such scenarios where vendor remediation is delayed, immediate mitigation strategies must be implemented by system administrators and security teams. The most effective short-term defense involves implementing strict input validation at the application layer to reject any label arguments containing path traversal characters before they reach the DLModelManager.get_model_meta function. Additionally, deploying a Web Application Firewall with rules specifically targeting directory traversal patterns can provide an additional layer of protection. Network segmentation should also be reviewed to ensure that even if file access is achieved, lateral movement within the internal network remains restricted. Organizations relying on BerryNet for critical infrastructure or sensitive data processing are strongly advised to monitor vendor communications closely and consider temporary workarounds until a patched version is released.