External risk intelligence

FreeIPA Trust Bypass Allows Active Directory User Privilege Escalation.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-11861

FreeIPA is commonly deployed as an identity management service and directory server. These services often feature internet-facing portals, LDAP interfaces, and authentication gateways to support remote users and distributed environments, making them commonly reachable in network architectures.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in FreeIPA, an identity management system, that could allow authenticated Active Directory users to bypass authentication for various FreeIPA services. This issue arises from an improper verification of Privilege Attribute Certificates, potentially enabling privilege escalation within the FreeIPA domain. The main concern is confirming relevance and exposure.

  • AD users can bypass FreeIPA authentication.
  • Impacts identity management and trust relationships.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could leverage a configured trust between FreeIPA and Active Directory to bypass authentication on FreeIPA services. This is achieved by impersonating a client name when requesting a Ticket Granting Service (TGS) because FreeIPA services do not validate Privilege Attribute Certificates (PAC). Successful exploitation allows an authenticated Active Directory user to escalate privileges within the FreeIPA domain.

  • Authenticated Active Directory user.
  • Impersonating a client name for TGS.
  • Privilege escalation within FreeIPA.

Live Threat

Current exploitation, exposure, and threat context

When a trust relationship is configured between FreeIPA and Active Directory, Active Directory users could bypass authentication for FreeIPA services like the portal, SMB server, and LDAP directory. This is because FreeIPA services may not verify Privilege Attribute Certificates (PAC) when a client name is impersonated in the Ticket Granting Service (TGS). This could enable an authenticated Active Directory user to escalate their privileges within the FreeIPA domain.

  • Active Directory users could access FreeIPA services.
  • Bypassing authentication may allow impersonation.
  • Privilege escalation within the FreeIPA domain.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership of this critical vulnerability likely falls to the platform or infrastructure team managing FreeIPA, in coordination with the security team responsible for the overall trust relationship with Active Directory. The first practical step is to identify all FreeIPA instances, confirm their reachability and business criticality, and then pinpoint the accountable owner for remediation planning and execution.

  • Platform or infrastructure team owns remediation.
  • Verify Active Directory trust configuration.
  • Plan coordinated authentication service updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is FreeIPA and how is it used?

FreeIPA is an integrated identity management solution that combines directory services, authentication, and policy management. Organizations use it to centralize user identities, manage access control, and provide single sign-on capabilities across Linux-based environments. It is frequently deployed to bridge identity gaps between different operating systems and directory services.

What does CVE-2026-11861 mean for authentication security?

This vulnerability is classified as CWE-266: Incorrect Privilege Assignment. It occurs because FreeIPA services fail to verify Privilege Attribute Certificates (PAC) during certain authentication requests. Essentially, the system trusts identity claims without independently validating the user's authorized privileges, allowing a weakness in how it processes trust-based credentials.

How does an attacker trigger this authentication bypass?

An attacker must already have an authenticated account within the trusted Active Directory environment. They exploit the flaw by impersonating a different client name when requesting a Ticket Granting Service (TGS) token from FreeIPA. This bug is specifically tied to cross-platform trust relationships; it does not trigger if there is no active trust configuration between FreeIPA and Active Directory.

Is my environment at risk according to Halo Surface Signal?

If you have configured a trust relationship between FreeIPA and Active Directory, you are potentially affected. Halo Surface Signal notes that FreeIPA is often deployed as a central directory or identity gateway, and because these services frequently host internet-facing portals or LDAP interfaces to support distributed users, they are often reachable within complex network architectures.

What is the first step to address this FreeIPA vulnerability?

Start by identifying every FreeIPA instance within your infrastructure that maintains a trust relationship with Active Directory. Once you have a complete inventory, verify the specific trust configurations and coordinate with the infrastructure or platform teams to plan for necessary authentication service updates or security patches.

References