CVE Tools
Track your stack

CVE-2026-13097

Ipa: privilege escalation via krbcanonicalname manipulation due to realm-unaware uniqueness enforcement in freeipa ldap datastore

No known exploitation. EPSS puts it in the 46th percentile. Fixed versions are out.

CVSS 3.18.7HighEPSS percentile46th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products6 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Red Hat Enterprise Linux 10Fixed builds0:4.13.4-1.el10_2, 8100020261007071200.143e9e98, 0:4.13.4-1.el9_8Stated by: CVE record
  • Red Hat Enterprise Linux 10.0 Extended Update SupportFixed builds0:4.12.2-15.el10_0.7Stated by: CVE record
  • Red Hat Enterprise Linux 8.8 Telecommunications Update ServiceFixed builds8080020261007080925.e581a9e4Stated by: CVE record
  • Red Hat Enterprise Linux 8.8 Update Services for SAP SolutionsFixed builds8080020261007080925.e581a9e4Stated by: CVE record
  • Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsFixed builds0:4.10.1-12.el9_2.7Stated by: CVE record

Versions as the sources state them. 2 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

A privilege escalation flaw was found in FreeIPA. The uniqueness constraint enforced on Kerberos principal name attributes in the 389-ds directory server does not properly account for equivalent representations of the same principal name, allowing a user with sufficient LDAP write privileges to create a service principal that impersonates an existing privileged one. This can lead to unauthorized acquisition of Kerberos service tickets for sensitive services, potentially resulting in full domain compromise.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

33 events over 61 days, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Patch availablepatch available, workaround available, workaround available, record updated, record updated
  3. Patch availableworkaround available, record updated
  4. Patch availableworkaround available, record updated
  5. Patch availableworkaround available, record updated
  6. Patch availableworkaround available, record updated

Affected products

And 5 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

Scored 8.7 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

Sources

References in the record

And 7 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat, not every advisory.