CVE-2026-19349

lemonldap-ng: Lemonldap::NG::Portal versions from 2.0.0 before 2.16.9, from 2.17.0 before 2.21.5, from 2.22.0 before 2.23.3 for Per...

CVE-2026-19349 is fixed in lemonldap-ng on 1 platform, first by DEBIAN-CVE-2026-19349, released August 13, 2026. It is not reported as exploited. Patch Radar priority: Urgent.

Urgent
CVSS
9.8
critical
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0082
57th percentile

Lemonldap::NG::Portal versions from 2.0.0 before 2.16.9, from 2.17.0 before 2.21.5, from 2.22.0 before 2.23.3 for Perl allow authentication bypass via an OAuth2 state parameter stored as an SSO session in the GitHub and LinkedIn backends. Before redirecting to the identity provider, extractFormInfo() creates the state session with the positional call `getApacheSession( undef, 1, 0, 'GitHubState' )`. getApacheSession() takes a session id followed by a named argument hash, so the trailing arguments become that hash, `kind` defaults to SSO, and the state is written to the global session storage as a regular SSO session. Its identifier is handed to the unauthenticated visitor as the state parameter of the redirection URL. Any visitor who reaches the GitHub or LinkedIn endpoint can replay that identifier as a session cookie and obtain a valid SSO session without authenticating. The session holds neither _user nor authenticationLevel, which the shipped bootstrap configuration accepts because it grants virtual hosts a "default => accept" access rule; deployments whose rules test the user or require an authentication level are less exposed. Only configurations with the GitHub or LinkedIn authentication module enabled are affected.

Where it's fixed

ProductFixed inFixReleased
Linux
lemonldap-ng · Debian 12.15 (bookworm) 2.16.1+ds-deb12u9 DEBIAN-CVE-2026-19349 Aug 13, 2026
lemonldap-ng · Debian 13.5 (trixie) 2.21.2+ds-1+deb13u3 DEBIAN-CVE-2026-19349 Aug 13, 2026
lemonldap-ng · Debian 14 2.23.3+ds-1 DEBIAN-CVE-2026-19349 Aug 13, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.