CVE-2026-78134: strongSwan EAP Authentication Bypass Vulnerability

CVE-2026-78134 Overview

CVE-2026-78134 is an incorrect access control vulnerability in strongSwan, an open-source IPsec-based VPN solution. The flaw affects the eap-ttls and eap-peap plugins in versions 4.5.0 through 6.0.7. The plugins fail to properly validate the inner Extensible Authentication Protocol (EAP) identity, which can be missing or mismatched with the outer identity. This weakness in authorization logic maps to [CWE-863] Incorrect Authorization. An attacker with limited privileges on the network can leverage the flaw to bypass identity validation, compromising confidentiality and integrity of authenticated VPN sessions.

Critical Impact

Authenticated attackers can bypass EAP identity binding in tunneled EAP methods, enabling impersonation of legitimate VPN users and unauthorized access to protected network resources.

Affected Products

• strongSwan 4.5.0 through 6.0.7
• Deployments using the eap-ttls plugin for tunneled EAP authentication
• Deployments using the eap-peap plugin for Protected EAP authentication

Discovery Timeline

• 2026-09-07 - strongSwan project publishes vulnerability advisory
• 2026-09-11 - CVE-2026-78134 published to NVD
• 2026-09-14 - Last updated in NVD database

Technical Details for CVE-2026-78134

Vulnerability Analysis

The vulnerability resides in strongSwan's implementation of EAP-TTLS (Tunneled Transport Layer Security) and EAP-PEAP (Protected EAP). Both protocols establish an outer TLS tunnel using an anonymous or pseudonymous outer identity, then perform inner EAP authentication inside the tunnel. Correct implementations must bind the inner EAP identity to the credentials verified during inner authentication.

The strongSwan plugins fail to enforce this binding. The inner EAP identity can be omitted entirely, or it can differ from the identity actually authenticated within the tunnel. This breaks the trust model where the server should authorize access based on the verified inner identity.

The issue impacts VPN gateways and network access servers using strongSwan for enterprise remote access or 802.1X authentication. Exploitation requires an attacker with valid low-privilege credentials to manipulate identity fields during the EAP exchange.

Root Cause

The root cause is missing validation logic in the eap-ttls and eap-peap plugin code paths. The plugins do not consistently verify that the inner EAP identity is present and matches the identity provided during the outer negotiation or the credentials used inside the tunnel. This authorization gap allows the server to accept authentication decisions that are not properly bound to a single verified identity.

Attack Vector

The attack occurs over the network against a strongSwan server accepting EAP-TTLS or EAP-PEAP connections. An attacker with valid credentials initiates a tunneled EAP session and manipulates the inner identity field, either by omitting it or supplying a different identity than the one authenticated. The server accepts the mismatch and grants access based on an incorrect identity assumption.

Refer to the strongSwan Blog CVE-2026-78134 Analysis for the protocol-level exchange details.

Detection Methods for CVE-2026-78134

Indicators of Compromise

• Authentication log entries showing successful EAP-TTLS or EAP-PEAP sessions where the outer and inner identities do not correlate to the same user
• VPN sessions where the assigned authorization profile differs from the profile expected for the connecting credential
• Unexpected privilege elevation or resource access following completion of a tunneled EAP handshake

Detection Strategies

• Enable verbose logging on strongSwan (charon.filelog) and audit EAP-Identity values across outer and inner exchanges for mismatches
• Correlate RADIUS accounting records against strongSwan ike-updown events to identify identity discrepancies
• Deploy network detection rules that flag EAP-TTLS or EAP-PEAP sessions completing without an inner EAP-Identity Response

Monitoring Recommendations

• Forward strongSwan authentication logs to a centralized SIEM for long-term identity correlation analysis
• Alert on any VPN session where the authenticated inner identity differs from the outer identity or is null
• Baseline normal EAP method usage per user and alert on deviations that could indicate tunneled identity manipulation

How to Mitigate CVE-2026-78134

Immediate Actions Required

• Upgrade strongSwan to version 6.1.0 or later, which contains the fix for the eap-ttls and eap-peap identity validation flaw
• Inventory all strongSwan deployments and identify servers using tunneled EAP methods for remote access or 802.1X
• Rotate credentials for accounts that authenticated through affected EAP-TTLS or EAP-PEAP configurations if unauthorized access is suspected

Patch Information

The strongSwan project addressed the vulnerability in release 6.1.0. Refer to the GitHub StrongSwan Release 6.1.0 notes for full change details and to the strongSwan Blog CVE-2026-78134 Analysis for the vendor's technical write-up.

Workarounds

• Disable the eap-ttls and eap-peap plugins in strongswan.conf if tunneled EAP methods are not required
• Restrict VPN access to certificate-based authentication (eap-tls) until patched builds are deployed
• Enforce strict RADIUS-side identity checks that reject sessions with mismatched outer and inner identities

# Configuration example: disable vulnerable plugins in strongswan.conf
charon {
    load_modular = yes
    plugins {
        eap-ttls {
            load = no
        }
        eap-peap {
            load = no
        }
    }
}