Synced 17 Sept 2026 15:07 UTC Account
← FreeIPA

FreeIPA vulnerabilities: known CVEs & security history

FreeIPA · Identity · 6 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all FreeIPA release lines — 6 in total. A CVE here doesn't mean your version is affected — check FreeIPA's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known FreeIPA CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-11861 critical 9.6 0% 2026
CVE-2026-13097 high 8.7 0% 2026
CVE-2026-19550 high 8.2 0% 2026
CVE-2026-73198 high 7.5 0% 2026
CVE-2026-73197 high 7.5 0% 2026
CVE-2026-73196 medium 4.3 0% 2026

Is my FreeIPA 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 FreeIPA version → · Monitor FreeIPA for new CVEs →

FreeIPA vulnerabilities — frequently asked

How many known vulnerabilities does FreeIPA have?

IsItPatched tracks 6 CVEs for FreeIPA. 1 is critical-severity and 4 high-severity. These span every release line — what matters is whether the version you run is affected.

Does FreeIPA have any actively-exploited vulnerabilities?

None of FreeIPA'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 FreeIPA vulnerability?

Among tracked issues, CVE-2026-11861 (CRITICAL, CVSS 9.6) ranks highest — a CWE-266 weakness.

Is FreeIPA safe to use?

It depends on the version. The latest supported FreeIPA 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: FreeIPA security status · FreeIPA end-of-life · actively-exploited CVEs. Always verify against FreeIPA's advisories — see our disclaimer.