CVE-2026-19349
SSO auth bypass in LemonLDAP::NG via OAuth2 state replay (GitHub/LinkedIn).
Is CVE-2026-19349 being exploited?
Not confirmed. CVE-2026-19349 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-19349?
CVE-2026-19349 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-19349?
Yes. A fix has been recorded for CVE-2026-19349. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19349 affect?
CVE-2026-19349 affects Lemonldap::NG::Portal 2.0.0 - 2.16.8, Lemonldap::NG::Portal 2.17.0 - 2.21.4, Lemonldap::NG::Portal 2.22.0 - 2.23.2, GitHub and LinkedIn authentication backends. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19349?
Upgrade to fixed versions (2.16.9 / 2.21.5 / 2.23.3) or disable GitHub/LinkedIn auth; harden session rules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can replay OAuth2 'state' identifier as a session cookie to obtain a valid SSO session and access protected applications.
Immediate action required