CVE-2026-13097

CRITICALPre-NVD 8.79.1
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-20. A secondary CVSS source baseline 8.7; sources differ by 0.4.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-63243 (ENISA EUVD) · GHSA-q4ph-46qc-4w6x (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.7
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 20, 2026

Last Modified

November 2, 2026

Advisory Details (2)

Auto-updated Aug 20, 2026
Patch available. Sources: redhat.
Red Hat

2515974 – (CVE-2026-13097) CVE-2026-13097 ipa: Privilege escalation via krbCanonicalName manipulation due to realm-unaware uniqueness enforcement in FreeIPA LDAP datastore

https://bugzilla.redhat.com/show_bug.cgi?id=2515974
Red HatMentions a patch (unverified)

CVE-2026-13097 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-13097

Vendor Advisories for CVE-2026-13097(10)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatipa-0:4.6.8-5.el7_9.252026-10-30redhat
redhatidm:DL1-8060020261008133528.ada582f12026-10-26redhat
redhatidm:DL1-8100020261007070536.823393f52026-10-15redhat
redhatidm:DL1-8080020261007071832.b0a6ceea2026-10-15redhat
redhatipa-0:4.10.1-12.el9_2.72026-10-14redhat
redhatipa-0:4.11.0-15.el9_4.92026-10-14redhat
redhatipa-0:4.12.2-14.el9_6.82026-10-14redhat
redhatipa-0:4.12.2-15.el10_0.72026-10-14redhat
redhatipa-0:4.13.4-1.el10_22026-09-28redhat
redhatipa-0:4.13.4-1.el9_82026-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
freeipa4.10.1+dfsg1-1+exp1 ... 4.9.11-2 (19 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
freeipa4.12.4-1, 4.12.4-2, 4.13.1-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 43× in last 7d / 180× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 518 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 418 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 04:26 UTCEG score recompute
  2. 2026-11-02 04:26 UTCVendor advisory
  3. 2026-11-02 04:26 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-02 03:33 UTCEG score recompute
  5. 2026-11-02 03:33 UTCVendor advisory
  6. 2026-11-02 03:33 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-11-01 22:32 UTCEG score recompute
  8. 2026-11-01 22:32 UTCVendor advisory
  9. 2026-11-01 22:32 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-10-31 20:29 UTCEG score recompute
  12. 2026-10-31 20:29 UTCVendor advisory
  13. 2026-10-31 20:29 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  15. 2026-10-30 18:26 UTCEG score recompute
  16. 2026-10-30 18:26 UTCVendor advisory
  17. 2026-10-30 18:26 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-30 17:40 UTCEG score recompute
  19. 2026-10-30 17:40 UTCVendor advisory
  20. 2026-10-30 17:40 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-30 16:34 UTCEG score recompute
  22. 2026-10-30 16:34 UTCVendor advisory
  23. 2026-10-30 16:33 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
Show 75 more
  1. 2026-10-29 14:31 UTCEG score recompute
  2. 2026-10-29 14:31 UTCVendor advisory
  3. 2026-10-29 14:31 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-10-28 12:28 UTCEG score recompute
  6. 2026-10-28 12:28 UTCVendor advisory
  7. 2026-10-28 12:28 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  9. 2026-10-27 10:26 UTCEG score recompute
  10. 2026-10-27 10:26 UTCVendor advisory
  11. 2026-10-27 10:26 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-26 14:31 UTCEG score recompute
  14. 2026-10-26 14:31 UTCVendor advisory
  15. 2026-10-26 14:30 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-26 14:03 UTCEG score recompute
  17. 2026-10-26 14:03 UTCVendor advisory
  18. 2026-10-26 14:03 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-26 03:09 UTCEG score recompute
  20. 2026-10-26 03:09 UTCVendor advisory
  21. 2026-10-26 03:09 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-25 14:49 UTCEG score recompute
  24. 2026-10-25 01:06 UTCEG score recompute
  25. 2026-10-25 01:06 UTCVendor advisory
  26. 2026-10-25 01:06 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-10-23 23:02 UTCEG score recompute
  29. 2026-10-23 23:02 UTCVendor advisory
  30. 2026-10-23 23:02 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  31. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  32. 2026-10-22 20:58 UTCEG score recompute
  33. 2026-10-22 20:58 UTCVendor advisory
  34. 2026-10-22 20:58 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  35. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-10-21 18:55 UTCEG score recompute
  37. 2026-10-21 18:55 UTCVendor advisory
  38. 2026-10-21 18:55 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-10-20 16:48 UTCEG score recompute
  41. 2026-10-20 16:48 UTCVendor advisory
  42. 2026-10-20 16:48 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  43. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  44. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-10-19 14:43 UTCEG score recompute
  46. 2026-10-19 14:43 UTCVendor advisory
  47. 2026-10-19 14:43 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  48. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-10-18 12:41 UTCVendor advisory
  50. 2026-10-18 12:40 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  51. 2026-10-18 05:03 UTCEG score recompute
  52. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-10-17 10:35 UTCEG score recompute
  54. 2026-10-17 10:35 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  55. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-10-16 08:30 UTCEG score recompute
  57. 2026-10-16 08:30 UTCVendor advisory
  58. 2026-10-16 08:29 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  59. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-10-15 06:25 UTCEG score recompute
  61. 2026-10-15 06:25 UTCVendor advisory
  62. 2026-10-15 06:25 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-10-15 05:28 UTCEG score recompute
  64. 2026-10-15 05:28 UTCVendor advisory
  65. 2026-10-15 05:28 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  66. 2026-10-14 23:27 UTCEG score recompute
  67. 2026-10-14 23:27 UTCVendor advisory
  68. 2026-10-14 23:27 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-10-14 22:34 UTCEG score recompute
  70. 2026-10-14 22:34 UTCVendor advisory
  71. 2026-10-14 22:34 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  72. 2026-10-14 20:27 UTCEG score recompute
  73. 2026-10-14 20:27 UTCVendor advisory
  74. 2026-10-14 20:27 UTCGHSA enrichmentGHSA-q4ph-46qc-4w6x · GitHub severity CRITICAL · GitHub CVSS 9.1
  75. 2026-10-14 19:55 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-13097?
CVE-2026-13097 is a critical-severity vulnerability; its CVE record was published on August 20, 2026. 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…
When was CVE-2026-13097 made public?
CVE-2026-13097 was made public on August 20, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 20, 2026. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-13097 actively exploited?
CVE-2026-13097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13097?
CVE-2026-13097 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + FIRST EPSS + GHSA into a combined EG score of 9.1 (CRITICAL).
How do I remediate CVE-2026-13097?
A fix for CVE-2026-13097 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-13097 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-13097

Explore →

Is Your Infrastructure Affected by CVE-2026-13097?

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

Book a Demo →Browse All CVEs