CVE-2026-19349

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-19349: 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

http://www.openwall.com/lists/oss-security/2026/08/16/2
generic

v2.23.3 · LemonLDAP NG / lemonldap-ng · GitLab

https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.23.3
generic

v2.21.5 LTS · LemonLDAP NG / lemonldap-ng · GitLab

https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.21.5
generic

v2.16.9 LTS · LemonLDAP NG / lemonldap-ng · GitLab

https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/releases/v2.16.9

Vendor Advisories for CVE-2026-19349(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:13 UTCGHSA enrichment
  2. 2026-08-21 00:52 UTCEG score recompute
  3. 2026-08-21 00:52 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 20:30 UTCGHSA enrichment
  6. 2026-08-20 16:09 UTCGHSA enrichment
  7. 2026-08-20 11:46 UTCGHSA enrichment
  8. 2026-08-20 07:24 UTCGHSA enrichment
  9. 2026-08-20 03:03 UTCGHSA enrichment
  10. 2026-08-19 22:42 UTCGHSA enrichment
  11. 2026-08-19 18:21 UTCEG score recompute
  12. 2026-08-19 18:21 UTCGHSA enrichment
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-19 13:25 UTCGHSA enrichment
  15. 2026-08-19 09:03 UTCGHSA enrichment
  16. 2026-08-19 04:39 UTCGHSA enrichment
  17. 2026-08-19 00:18 UTCGHSA enrichment
  18. 2026-08-18 19:56 UTCGHSA enrichment
  19. 2026-08-18 15:35 UTCEG score recompute
  20. 2026-08-18 15:35 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-18 11:09 UTCGHSA enrichment
  23. 2026-08-18 06:43 UTCGHSA enrichment
  24. 2026-08-18 02:21 UTCGHSA enrichment
  25. 2026-08-17 21:51 UTCEG score recompute
Show 11 more
  1. 2026-08-17 21:50 UTCGHSA enrichment
  2. 2026-08-17 17:26 UTCEG score recompute 9.80
  3. 2026-08-17 17:25 UTCGHSA enrichment
  4. 2026-08-17 17:24 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 17:20 UTCNVD update
  7. 2026-08-16 17:17 UTCGHSA enrichment
  8. 2026-08-16 17:16 UTCMITRE cvelistV5
  9. 2026-08-16 14:35 UTCNVD update
  10. 2026-08-16 13:42 UTCEG score recompute
  11. 2026-08-16 13:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19349?
CVE-2026-19349 is a critical vulnerability published on August 16, 2026. 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,…
When was CVE-2026-19349 disclosed?
CVE-2026-19349 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19349 actively exploited?
CVE-2026-19349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.6% of all scored CVEs.
What is the CVSS score of CVE-2026-19349?
CVE-2026-19349 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19349?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19349, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19349

Explore →

Is Your Infrastructure Affected by CVE-2026-19349?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.