pfSense vulnerabilities: known CVEs & security history
Netgate · Network security · 6 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all pfSense release lines — 6 in total. A CVE here doesn't mean your version is affected — check pfSense's current status and the safe version to run.
Known pfSense CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-34175 | medium | 6.1 | 15% | 2025 |
| CVE-2025-34172 | medium | 6.1 | 1% | 2025 |
| CVE-2025-34178 | medium | 5.4 | 3% | 2025 |
| CVE-2025-34177 | medium | 5.4 | 1% | 2025 |
| CVE-2025-34176 | medium | 4.3 | 14% | 2025 |
| CVE-2025-34173 | medium | 4.3 | 1% | 2025 |
Is my pfSense version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your pfSense version → · Monitor pfSense for new CVEs →
pfSense vulnerabilities — frequently asked
How many known vulnerabilities does pfSense have?
IsItPatched tracks 6 CVEs for pfSense. 0 are critical-severity and 0 high-severity. These span every release line — what matters is whether the version you run is affected.
Does pfSense have any actively-exploited vulnerabilities?
None of pfSense's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe pfSense vulnerability?
Among tracked issues, CVE-2025-34175 (MEDIUM, CVSS 6.1) ranks highest — a Cross-site scripting (XSS) weakness.
Is pfSense safe to use?
It depends on the version. The latest supported pfSense release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: pfSense security status · pfSense end-of-life · actively-exploited CVEs. Always verify against Netgate's advisories — see our disclaimer.