REDHAT-BUG-2519522: FreeIPA vulnerability

Published Aug 19, 2026
·
Updated

An unauthenticated LDAP client (anonymous bind or SASL ANONYMOUS) can create a self-managed OTP token entry with empty ipaTokenOwner/managedBy attributes, which satisfy 389 Directory Server's SELFDN ACI evaluator against the anonymous bind's own empty DN (see companion 389-ds flaw for that underlying defect). FreeIPA's self-managed-token ACI (install/share/default-aci.ldif) does not restrict which other attributes may be added, allowing the client to inject a Kerberos principal and password. Combined with a canonical-principal mismatch and, on older releases, a password-expiration-bypass, this produces genuine, reusable FreeIPA administrator Kerberos credentials. On SID-enabled deployments, the anonymously-readable ipaNTSecurityIdentifier attribute lets the attacker also obtain a PAC-bearing TGT, extending access to HTTP/Dogtag.

Independently reproduced twice against a stock, unmodified freeipa/freeipa-server:almalinux-10 (FreeIPA 4.13.1) install — most recently from a client with zero prior access (no ticket, no local presence, network reachability only). Verified beyond the PoC's own output via klist -f, ldapwhoami -Y GSSAPI (returned genuine admin DN), ldapcompare (confirmed cn=admins membership), and a real admin-only write/delete (ipa user-add / ipa user-del).

Reported by Gia Bui (Calif.io) via PSIRTSUPT-21812; see linked ticket for full technical writeup, reporter PoC, and reproduction logs.

Affected Software

1 affected component
FreeIPA=4.13.1

Event History

Aug 19, 2026
Data Sourced
via Red Hat·12:32 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What access does an attacker need to exploit this?

The issue was reproduced from a client with no prior access: no Kerberos ticket, no local presence, and only network reachability to the target. The attacker uses an unauthenticated LDAP connection through an anonymous bind or SASL ANONYMOUS.

2

Is a default deployment affected?

The issue was independently reproduced against a stock, unmodified freeipa/freeipa-server:almalinux-10 installation running FreeIPA 4.13.1. The vulnerable self-managed-token ACI is identified as install/share/default-aci.ldif.

3

What level of access can successful exploitation provide?

Successful exploitation can create genuine, reusable FreeIPA administrator Kerberos credentials. Validation included a Kerberos ticket listing, GSSAPI LDAP authentication returning the genuine administrator DN, and LDAP comparison checks.

4

Does SID support change the impact?

Yes. On SID-enabled deployments, the anonymously readable ipaNTSecurityIdentifier attribute can allow the attacker to obtain a PAC-bearing TGT, extending access to HTTP/Dogtag.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203