ftldns vulnerabilities and fixes
Recent CVEs affecting ftldns, with upgrade or downgrade steps. 6 tracked.
ftldns has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2026-04-07. Highest priority: CVE-2026-35517 (score 50/100).
- CVE-2026-35517 HIGH 8.8 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
- CVE-2026-35491 MEDIUM 6.1 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
- CVE-2026-35518 HIGH 8.8 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
- CVE-2026-35520 HIGH 8.8 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
- CVE-2026-35521 HIGH 8.8 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
- CVE-2026-35519 HIGH 8.8 UPGRADE FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface
FAQ
How do I fix ftldns vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ftldns being exploited right now?
None of the tracked ftldns CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ftldns CVE should I patch first?
CVE-2026-35517 currently ranks highest (50/100): FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface.