/

CVE-2026-41070

Severity:

CRITICAL RISK

(10.0)

Improper Authentication (CWE-287) in openvpn-auth-oauth2

CVE-2026-41070

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Unauthorized VPN Access and Account Impersonation

Severity:

CRITICAL RISK

(10.0)

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 critical improper-authentication vulnerability affects openvpn-auth-oauth2, a plugin and management-interface client that handles OpenID Connect single sign-on flows for OpenVPN servers.

If authentication responses or identity assertions are not adequately verified, an attacker may be able to obtain unauthorized VPN access or impersonate a legitimate user. The available description does not specify the exact protocol condition or exploit path.

Affected context

The issue applies to deployments using openvpn-auth-oauth2 from version 1.26.3 and relying on its OIDC-based SSO integration with an OpenVPN server. Risk depends on how authentication responses, identity claims, tokens, redirect handling, and session establishment are validated; the provided vulnerability information does not identify the precise failing validation.

Exploit preconditions

  • Attack surface: The OpenVPN authentication and management-interface integration exposed by the plugin
  • Required access: The attacker may need network reachability to the relevant authentication flow; the exact access level is not specified
  • Trigger point: Processing an OIDC authentication result or establishing an authenticated OpenVPN session
  • Why exploitation is possible: Authentication state or identity information may be accepted without sufficient verification, potentially allowing an unauthenticated or incorrectly authenticated party to be treated as a valid user

Why this happens

The underlying bug class is improper authentication, mapped to CWE-287. This occurs when software fails to reliably establish that a requester or presented identity is the legitimate principal it claims to be. In an OIDC-backed VPN login flow, insecure trust decisions around tokens, claims, issuer information, redirect state, or session binding could allow authentication to succeed without adequate proof of identity. The specific deficient check is not described in the available advisory information.

Potential impact

  • An attacker may gain unauthorized access to VPN-protected resources
  • A malicious party could impersonate a legitimate SSO user
  • Compromised sessions may enable access to internal services reachable through the VPN
  • Security monitoring and authorization decisions could be based on a forged or incorrectly accepted identity

General mitigation guidance

Mitigation generally focuses on making authentication decisions depend only on fully validated identity evidence.

Common defensive patterns include:

  • Enforcing strict OIDC issuer, audience, signature, expiration, nonce, and state validation
  • Binding authentication responses and sessions to the initiating client and expected redirect flow
  • Rejecting missing, malformed, expired, or ambiguously mapped identity claims
  • Applying least privilege to VPN users and limiting access through explicit authorization policies
  • Avoiding fallback authentication behavior that can bypass the SSO verification path
  • Protecting management interfaces and authentication endpoints with restricted network access and appropriate monitoring

How teams detect issues like this

Organizations can assess for improper-authentication risks through:

  • Static analysis and code review of token, claim, issuer, redirect, nonce, and session-validation logic
  • Tests that submit expired, malformed, mismatched, unsigned, or incorrectly scoped identity assertions
  • Review signals such as trusting client-supplied identity fields or accepting authentication before state and issuer checks complete
  • Monitoring for successful VPN logins that lack a corresponding validated identity-provider event
  • Policy enforcement requiring documented OIDC validation controls and negative authentication tests in CI
  • Neutral automated security-review tools that flag authentication decisions based on unverified external data

Sources

SourceLink
github.comgithub.com/jkroepke/openvpn-auth-oauth2/commit/36f69a6c67c1054da7cbfa04ced3f0555127c8f2
github.comgithub.com/jkroepke/openvpn-auth-oauth2/security/advisories/GHSA-246w-jgmq-88fg

Frequently asked

questions

The available description does not establish the exact exploit path. Because the affected component participates in an OpenVPN SSO flow, exploitation could be remotely reachable when the authentication interface is network-accessible, but the precise scope depends on deployment configuration.

Not necessarily. Improper-authentication vulnerabilities can permit access without legitimate credentials, although the required conditions for this issue are not specified.

Ensure that every OIDC authentication response is validated against the expected issuer, audience, signature, lifetime, state, nonce, and identity-mapping rules before creating a VPN session.

Use well-tested OIDC libraries, apply strict server-side validation, limit management-interface exposure, enforce least-privilege VPN authorization, and include negative authentication tests in security reviews and CI pipelines.

Find out what's already
exploitable in your codebase.