/

CVE-2026-78134

Severity:

HIGH RISK

(7.1)

Incorrect Access Control (CWE-863) in strongSwan EAP

CVE-2026-78134

Analyzed

Vulnerability type

Category:

Incorrect Access Control

CWE:

CWE-863

Impact:

Unauthorized access or identity misbinding

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing or mismatched inner EAP identity in strongSwan's eap-ttls and eap-peap plugins can cause authorization decisions to rely on inconsistent identity information. Under affected authentication configurations, an attacker may gain access that should have been denied or be associated with the wrong identity.

Affected context

The issue occurs in strongSwan deployments using the eap-ttls or eap-peap plugins where an outer EAP exchange and its inner authentication identity are not consistently required to match. Risk depends on the authentication policy, identity mapping, and authorization rules applied after EAP authentication.

Exploit preconditions

  • Attack surface: EAP authentication through a strongSwan endpoint
  • Required access: Network access to initiate or participate in an applicable EAP authentication exchange
  • Trigger point: Processing and authorization of an EAP-TTLS or EAP-PEAP session with a missing or mismatched inner identity
  • Why exploitation is possible: Access-control decisions may be made without reliably binding the authenticated session to the expected inner EAP identity

Why this happens

The underlying bug is an authorization control that does not consistently verify the relationship between the outer EAP identity and the inner identity used for authentication. This permits identity information to be absent or inconsistent while the session continues through authorization logic. The behavior maps to CWE-863: Incorrect Authorization, because access decisions may not be enforced against the correct authenticated principal.

Potential impact

  • An attacker may obtain access intended for another identity
  • Authorization policies could be applied to the wrong principal
  • Network access restrictions may be bypassed
  • Audit records may associate activity with an inaccurate identity
  • A compromised account could gain broader access than intended

General mitigation guidance

Mitigation generally focuses on enforcing identity consistency throughout authentication and authorization.

Common defensive patterns include:

  • Require a valid inner EAP identity whenever the selected authentication method depends on it
  • Bind authorization decisions to the verified inner identity rather than relying on untrusted outer identity data
  • Reject missing, malformed, or mismatched identity values by default
  • Apply explicit allowlists and least-privilege network authorization policies
  • Limit the permissions available to identities authenticated through tunneled EAP methods
  • Review identity mapping and logging so authentication and authorization records use the same verified principal

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for authorization paths that accept optional or inconsistent identity fields
  • Tests covering missing, conflicting, and reordered outer and inner EAP identities
  • Authentication-policy reviews that verify identity binding before access is granted
  • Runtime monitoring for successful sessions with absent or inconsistent inner identities
  • Policy enforcement requiring explicit rejection of identity mismatches

Automated security review tools may help identify unchecked identity comparisons and authorization decisions made before principal verification.

Sources

SourceLink
github.comgithub.com/strongswan/strongswan/releases/tag/6.1.0
strongswan.orgstrongswan.org/blog/2026/09/07/strongswan-vulnerability-(cve-2026-78134).html

Frequently asked

questions

It may be reachable over the network when a strongSwan endpoint accepts EAP-TTLS or EAP-PEAP authentication, but practical exploitability depends on the configured authentication and authorization policies.

An attacker generally needs network connectivity to initiate an applicable EAP authentication exchange. The required credentials and other conditions depend on the deployment configuration.

Enforce the presence and consistency of the inner EAP identity, bind authorization to the verified identity, and reject mismatches by default.

Use positive identity binding, least-privilege authorization, negative tests for missing or conflicting identities, and monitoring that compares authentication records with authorization decisions.

Find out what's already
exploitable in your codebase.