Bug 2558280 (CVE-2026-114417)

Summary: CVE-2026-114417 phodav: Path traversal in WebDAV MOVE/COPY via encoded slashes in Destination header
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2569222    
Bug Blocks:    

Description OSIDB Bzimport 2026-10-21 12:57:27 UTC
A path traversal vulnerability was found in phodav's WebDAV MOVE/COPY handlers (libphodav/phodav-method-movecopy.c). The Destination header is parsed with g_uri_parse() which preserves encoded slashes (%2F) through dot-segment removal. After full unescaping, g_file_get_child() resolves ".." components outside the shared root directory. A remote attacker can exploit this to create, copy, or move files to arbitrary filesystem locations writable by the server user, outside of the shared directory. Since the copied content can be attacker-controlled (via a prior PUT), this enables arbitrary file write as the server user. Many deployments (chezdav default, spice-gtk folder sharing) run without authentication, making this exploitable without credentials. The vulnerable pattern has been present since phodav v0.4 (April 2014) and affects all versions through 3.0.