CVE-2026-35025

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ProFTPD through 1.3.9b and 1.3.10rc2 contains an access control bypass vulnerability that allows authenticated FTP users to circumvent Directory ACL restrictions by prefixing paths with /proc/self/root in the RNFR command handler. Attackers can exploit the unresolved symlink components in dir_canonical_path() to cause dir_check() to perform lexical path comparisons that match no configured Directory block, enabling rename operations on files in DenyAll-protected directories and subsequent retrieval of those files. Mitigation: Sessions configured with DefaultRoot (chroot) are not affected, as chroot changes the directory to which /proc/self/root resolves.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
25.0%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

ProFTPD ACL Bypass via /proc/self/root Path Prefix in RNFR | Advisories | VulnCheck

https://www.vulncheck.com/advisories/proftpd-acl-bypass-via-proc-self-root-path-prefix-in-rnfr
generic

Security Advisory: Post-authentication access control bypass via `/proc/self/root` in `RNFR` · Issue #2170 · proftpd/proftpd · GitHub

https://github.com/proftpd/proftpd/issues/2170
generic

The ProFTPD Project: Home

http://www.proftpd.org/

Vendor Advisories for CVE-2026-35025(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:34 UTCEG score recompute
  2. 2026-07-06 23:34 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:47 UTCEG score recompute
  6. 2026-07-06 11:47 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:59 UTCEG score recompute
  10. 2026-07-05 23:59 UTCGHSA enrichment
  11. 2026-07-05 12:12 UTCEG score recompute
  12. 2026-07-05 12:12 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 00:26 UTCEG score recompute
  15. 2026-07-05 00:26 UTCGHSA enrichment
  16. 2026-07-04 12:33 UTCEG score recompute
  17. 2026-07-04 12:32 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 00:45 UTCEG score recompute
  20. 2026-07-04 00:45 UTCGHSA enrichment
  21. 2026-07-03 12:50 UTCEG score recompute
  22. 2026-07-03 12:50 UTCGHSA enrichment
  23. 2026-07-03 00:25 UTCEG score recompute
  24. 2026-07-03 00:25 UTCGHSA enrichment
  25. 2026-07-02 12:38 UTCEG score recompute
Show 45 more
  1. 2026-07-02 12:38 UTCGHSA enrichment
  2. 2026-07-02 00:46 UTCEG score recompute
  3. 2026-07-02 00:46 UTCGHSA enrichment
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 12:54 UTCEG score recompute
  6. 2026-07-01 12:54 UTCGHSA enrichment
  7. 2026-07-01 01:08 UTCEG score recompute
  8. 2026-07-01 01:08 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 13:21 UTCEG score recompute
  11. 2026-06-30 13:21 UTCGHSA enrichment
  12. 2026-06-30 01:34 UTCEG score recompute
  13. 2026-06-30 01:34 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 13:48 UTCEG score recompute
  17. 2026-06-29 13:48 UTCGHSA enrichment
  18. 2026-06-29 02:01 UTCEG score recompute
  19. 2026-06-29 02:01 UTCGHSA enrichment
  20. 2026-06-28 14:15 UTCEG score recompute
  21. 2026-06-28 14:15 UTCGHSA enrichment
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-28 02:29 UTCEG score recompute
  27. 2026-06-28 02:29 UTCGHSA enrichment
  28. 2026-06-27 14:43 UTCEG score recompute
  29. 2026-06-27 14:43 UTCGHSA enrichment
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-27 02:56 UTCEG score recompute
  32. 2026-06-27 02:56 UTCGHSA enrichment
  33. 2026-06-26 15:10 UTCEG score recompute
  34. 2026-06-26 15:09 UTCGHSA enrichment
  35. 2026-06-26 03:23 UTCEG score recompute
  36. 2026-06-26 03:23 UTCGHSA enrichment
  37. 2026-06-25 15:37 UTCEG score recompute
  38. 2026-06-25 15:37 UTCGHSA enrichment
  39. 2026-06-25 13:49 UTCEPSS rescore
  40. 2026-06-25 13:49 UTCEPSS rescore
  41. 2026-06-25 03:50 UTCEG score recompute
  42. 2026-06-25 03:50 UTCGHSA enrichment
  43. 2026-06-24 18:02 UTCNVD updateCVSS v4 → 8.6
  44. 2026-06-24 16:03 UTCEG score recompute
  45. 2026-06-24 16:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-35025?
CVE-2026-35025 is a high vulnerability published on June 24, 2026. ProFTPD through 1.3.9b and 1.3.10rc2 contains an access control bypass vulnerability that allows authenticated FTP users to circumvent Directory ACL restrictions by prefixing paths with /proc/self/root in the RNFR command handler. Attackers can exploit the unresolved symlink components in…
When was CVE-2026-35025 disclosed?
CVE-2026-35025 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35025 actively exploited?
CVE-2026-35025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-35025?
CVE-2026-35025 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-35025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35025, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-35025

Explore →

Is Your Infrastructure Affected by CVE-2026-35025?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.