CVE-2026-35025
Auth bypass in ProFTPD allows renaming in restricted dirs via /proc/self/root in RNFR.
Is CVE-2026-35025 being exploited?
Not confirmed. CVE-2026-35025 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-35025?
CVE-2026-35025 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-35025?
Yes. A fix has been recorded for CVE-2026-35025. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35025 affect?
CVE-2026-35025 affects ProFTPD 1.3.9b, ProFTPD 1.3.10rc2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35025?
Upgrade to patched ProFTPD when available; enforce ACLs and chroot where possible.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated FTP users can bypass ACLs and access/rename files in DenyAll-protected directories via RNFR path manipulation.
Patch when possible
- affected<= 1.3.9b
- affected<= 1.3.10rc2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.