Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-92289 – OIDC PKCE Bypass / Authentication Bypass – Lemonldap::NG::Portal 2.23.0–2.23.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-92289 is an authentication bypass vulnerability in Lemonldap::NG::Portal, the identity/access management and web SSO portal component of the Lemonldap::NG suite. It allows an attacker to bypass Proof Key for Code Exchange (PKCE) protections and exchange an intercepted OAuth2/OpenID Connect authorization code for a victim’s tokens by replaying the client_id with an arbitrary secret. The issue is rated CRITICAL (CVSS 9.1) and is remotely exploitable without authentication or user interaction.

Technical details

  • Root cause: the checkEndPointAuthenticationCredentials function in lib/Lemonldap/NG/Portal/Lib/OpenIDConnect.pm / lib/Lemonldap/NG/Portal/Issuer/OpenIDConnect.pm does not verify the client secret for Relying Parties (RPs) marked as "public," yet still returns an authentication method as if credentials were validated.
  • Trigger condition: occurs when a public Relying Party’s RequirePKCE option is set to "PKCE or secret" mode. The authorization endpoint can issue a code even without a code_challenge, and the token endpoint’s validatePKCEChallenge() check passes trivially because neither a challenge nor a verifier is present.
  • Attack vector: network-based, low complexity, no privileges or user interaction required. An attacker who intercepts (or otherwise obtains) an authorization code issued to a public RP can replay the client_id together with an arbitrary/fabricated secret at the token endpoint to complete the code exchange.
  • Impact: successful exploitation lets an attacker obtain a legitimate user’s OIDC access, ID, and refresh tokens, enabling impersonation of the user or application and unauthorized access to protected resources and personal data. Confidentiality and integrity impacts are high; there is no availability impact.

Affected software

  • Lemonldap::NG::Portal (Perl/CPAN module, part of the Lemonldap::NG suite) — versions 2.23.0 through 2.23.3 (i.e., before 2.23.4)
  • A related, separately tracked issue (CVE-2026-92288) affects the same checkEndPointAuthenticationCredentials code path in additional version ranges; environments should confirm they are patched against both.

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Lemonldap::NG::Portal to version 2.23.4 or later, which fixes the credential/PKCE validation logic.
  • If patching is not immediately possible:
    • Enforce strict PKCE requirements ("PKCE required," not "PKCE or secret") on all public Relying Parties so token exchange cannot fall back to secret-based validation without a valid challenge/verifier pair.
    • Disable or restrict dynamic client registration for public clients where not strictly necessary.
    • Review OIDC/OAuth2 authorization and token endpoint logs for anomalous code-exchange requests referencing public client_ids.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge