Authenticated ACL bypass via unresolved procfs symlink
Published Jun 24, 2026 · Updated Jun 24, 2026
Access control bypass in ProFTPD 1.3.9b and earlier and 1.3.10rc2 and earlier allows remote authenticated users to retrieve restricted files. The RNFR handler leaves /proc/self/root symlink components unresolved in dir_canonical_path(), so dir_check() compares a lexical path that matches no Directory ACL and permits a protected-file rename. Exploitation requires valid FTP credentials, a DenyAll-protected path, and a session without DefaultRoot; the consequence is unauthorized file retrieval.
Summary
What happened
Access control bypass in ProFTPD 1.3.9b and earlier and 1.3.10rc2 and earlier allows remote authenticated users to retrieve restricted files. The RNFR handler leaves /proc/self/root symlink components unresolved in dir_canonical_path(), so dir_check() compares a lexical path that matches no Directory ACL and permits a protected-file rename. Exploitation requires valid FTP credentials, a DenyAll-protected path, and a session without DefaultRoot; the consequence is unauthorized file retrieval.
The record
- CVE
- CVE-2026-35025
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- ProFTPD Project
- Product
- ProFTPD
- Classifications
- CWE-59, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.3.10rc2
- Affected versionversion=0 <=1.3.9b
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo