CVE-2026-19349: CWE-305 Authentication Bypass by Primary Weakness
Lemonldap::NG::Portal versions 2.0.0, 2.17.0, and 2.22.0 are affected by an authentication bypass vulnerability in the GitHub and LinkedIn OAuth2 backends. The flaw arises because the OAuth2 state parameter is stored as a regular SSO session, allowing unauthenticated visitors to replay the session identifier and gain a valid SSO session without authentication. This vulnerability affects only configurations with the GitHub or LinkedIn authentication modules enabled and is influenced by access rules in the deployment configuration.
AI Analysis
Technical Summary
CVE-2026-19349 is an authentication bypass vulnerability in Lemonldap::NG::Portal affecting versions 2.0.0, 2.17.0, and 2.22.0. The issue stems from the OAuth2 state parameter being stored as a standard SSO session via a positional call to getApacheSession() that misinterprets arguments, causing the state to be written globally as an SSO session. An unauthenticated visitor can replay the session identifier as a cookie at the GitHub or LinkedIn endpoint to obtain a valid SSO session without authenticating. The session lacks user and authentication level attributes, but the default bootstrap configuration grants access based on a "default => accept" rule, making some deployments more vulnerable than others depending on their access control rules.
Potential Impact
An attacker who can reach the GitHub or LinkedIn OAuth2 endpoint can bypass authentication by replaying a session identifier, gaining unauthorized access to a valid SSO session. This could allow unauthorized access to resources protected by Lemonldap::NG::Portal when using the affected authentication modules. The impact depends on the deployment's access control configuration; those relying on default accept rules are more exposed, while deployments requiring user or authentication level checks are less affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, deployments should review and tighten access control rules to avoid relying on default accept rules and ensure authentication level or user presence is required. Disabling the GitHub and LinkedIn authentication modules if not needed can also reduce exposure.
CVE-2026-19349: CWE-305 Authentication Bypass by Primary Weakness
Description
Lemonldap::NG::Portal versions 2.0.0, 2.17.0, and 2.22.0 are affected by an authentication bypass vulnerability in the GitHub and LinkedIn OAuth2 backends. The flaw arises because the OAuth2 state parameter is stored as a regular SSO session, allowing unauthenticated visitors to replay the session identifier and gain a valid SSO session without authentication. This vulnerability affects only configurations with the GitHub or LinkedIn authentication modules enabled and is influenced by access rules in the deployment configuration.
Affected software
pkg:github/lemonldap-ng/lemonldap-ngRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-19349 is an authentication bypass vulnerability in Lemonldap::NG::Portal affecting versions 2.0.0, 2.17.0, and 2.22.0. The issue stems from the OAuth2 state parameter being stored as a standard SSO session via a positional call to getApacheSession() that misinterprets arguments, causing the state to be written globally as an SSO session. An unauthenticated visitor can replay the session identifier as a cookie at the GitHub or LinkedIn endpoint to obtain a valid SSO session without authenticating. The session lacks user and authentication level attributes, but the default bootstrap configuration grants access based on a "default => accept" rule, making some deployments more vulnerable than others depending on their access control rules.
Potential Impact
An attacker who can reach the GitHub or LinkedIn OAuth2 endpoint can bypass authentication by replaying a session identifier, gaining unauthorized access to a valid SSO session. This could allow unauthorized access to resources protected by Lemonldap::NG::Portal when using the affected authentication modules. The impact depends on the deployment's access control configuration; those relying on default accept rules are more exposed, while deployments requiring user or authentication level checks are less affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, deployments should review and tighten access control rules to avoid relying on default accept rules and ensure authentication level or user presence is required. Disabling the GitHub and LinkedIn authentication modules if not needed can also reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-08-08T14:18:36.846Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a81be1abf8831d539265657
Added to database: 08/16/2026, 13:41:46 UTC
Last enriched: 08/16/2026, 13:59:07 UTC
Last updated: 08/16/2026, 14:35:30 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.