CVE-2026-114417
Description
A flaw was found in phodav. Improper handling of encoded path separators in WebDAV MOVE and COPY requests leads to a path traversal vulnerability. A remote attacker can exploit this issue by sending a specially crafted request with directory traversal sequences in the Destination header. Successful exploitation allows the attacker to write or overwrite files in arbitrary filesystem locations accessible by the server process.
Statement
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.
Mitigation
If WebDAV folder sharing is not required in guest virtual machines, stop and mask the spice-webdavd service:
systemctl stop spice-webdavd
systemctl mask spice-webdavd
If the service or standalone chezdav server is required, restrict network access to the listening port using firewall rules to allow connections only from trusted hosts or localhost:
firewall-cmd --permanent --zone=public --remove-port=8080/tcp
firewall-cmd --reload
Caveats:
Disabling spice-webdavd prevents shared folder functionality between the host and virtual machine guests.
Warning:
Stopping the service terminates active file transfer sessions immediately. Modifying and reloading firewall rules may temporarily interrupt network connectivity.
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.
Acknowledgements
Red Hat would like to thank uc.surf security research for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.