CVE-2026-76806
Description
A flaw was found in solidtime. An authenticated remote attacker can exploit this vulnerability by uploading a specially crafted archive file containing directory traversal sequences during a Toggl data import. Successful exploitation allows the attacker to bypass directory restrictions, create directories in arbitrary writable host locations, and infer the existence of host files from application responses.
Statement
This vulnerability is rated as having Moderate impact because exploitation requires authenticated access to the Toggl import interface and the impact is limited to creating empty directories and probing file existence, rather than arbitrary file modification or remote code execution. Solidtime is not packaged or distributed in Red Hat enterprise offerings, and default environments do not expose this software. Consequently, the flaw presents no direct operational impact on supported Red Hat products.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
