CVE-2026-19349

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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 — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

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.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 16, 2026

Last Modified

August 26, 2026

Advisory Details (4)

Auto-updated Sep 30, 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.

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lemonldap-ng2.16.1+ds-2 ... 2.16.1+ds-deb12u8 (9 versions)
  • every version up to 2.16.1+ds-deb12u9: fixed in 2.16.1+ds-deb12u9
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lemonldap-ng2.21.2+ds-1, 2.21.2+ds-1+deb13u1, 2.21.2+ds-1+deb13u2
  • every version up to 2.21.2+ds-1+deb13u3: fixed in 2.21.2+ds-1+deb13u3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 172× 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.

Showing the most recent 100 of 312 total refreshes for this CVE.

  1. 2026-10-05 06:44 UTCGHSA enrichment
  2. 2026-10-05 02:23 UTCGHSA enrichment
  3. 2026-10-04 21:52 UTCGHSA enrichment
  4. 2026-10-04 16:26 UTCGHSA enrichment
  5. 2026-10-04 12:03 UTCGHSA enrichment
  6. 2026-10-04 07:42 UTCGHSA enrichment
  7. 2026-10-04 03:21 UTCGHSA enrichment
  8. 2026-10-03 19:25 UTCEG score recompute
  9. 2026-10-03 19:25 UTCGHSA enrichment
  10. 2026-10-03 02:08 UTCGHSA enrichment
  11. 2026-10-02 21:45 UTCEG score recompute
  12. 2026-10-02 21:45 UTCGHSA enrichment
  13. 2026-10-02 15:48 UTCGHSA enrichment
  14. 2026-10-02 06:59 UTCGHSA enrichment
  15. 2026-10-02 01:57 UTCEG score recompute
  16. 2026-10-02 01:57 UTCGHSA enrichment
  17. 2026-10-01 19:49 UTCEPSS rescore
  18. 2026-10-01 14:35 UTCGHSA enrichment
  19. 2026-10-01 10:13 UTCGHSA enrichment
  20. 2026-10-01 05:52 UTCGHSA enrichment
  21. 2026-10-01 01:31 UTCGHSA enrichment
  22. 2026-09-30 20:53 UTCEG score recompute
  23. 2026-09-30 20:53 UTCGHSA enrichment
  24. 2026-09-30 15:02 UTCEPSS rescore
  25. 2026-09-30 12:00 UTCEG score recompute
Show 75 more
  1. 2026-09-30 12:00 UTCGHSA enrichment
  2. 2026-09-29 15:20 UTCEPSS rescore
  3. 2026-09-29 06:48 UTCGHSA enrichment
  4. 2026-09-29 02:27 UTCGHSA enrichment
  5. 2026-09-28 22:01 UTCEG score recompute
  6. 2026-09-28 22:01 UTCGHSA enrichment
  7. 2026-09-28 13:51 UTCEPSS rescore
  8. 2026-09-28 11:33 UTCGHSA enrichment
  9. 2026-09-28 07:09 UTCGHSA enrichment
  10. 2026-09-28 02:48 UTCGHSA enrichment
  11. 2026-09-27 22:27 UTCGHSA enrichment
  12. 2026-09-27 17:03 UTCEG score recompute
  13. 2026-09-27 17:03 UTCGHSA enrichment
  14. 2026-09-27 13:47 UTCEPSS rescore
  15. 2026-09-27 12:41 UTCGHSA enrichment
  16. 2026-09-27 08:20 UTCEG score recompute
  17. 2026-09-27 08:20 UTCGHSA enrichment
  18. 2026-09-26 15:58 UTCEPSS rescore
  19. 2026-09-25 11:52 UTCGHSA enrichment
  20. 2026-09-25 06:38 UTCGHSA enrichment
  21. 2026-09-25 02:17 UTCGHSA enrichment
  22. 2026-09-24 16:20 UTCEG score recompute
  23. 2026-09-24 16:20 UTCGHSA enrichment
  24. 2026-09-24 09:33 UTCGHSA enrichment
  25. 2026-09-24 05:12 UTCGHSA enrichment
  26. 2026-09-24 00:50 UTCGHSA enrichment
  27. 2026-09-23 20:29 UTCGHSA enrichment
  28. 2026-09-23 14:09 UTCEG score recompute
  29. 2026-09-23 14:09 UTCGHSA enrichment
  30. 2026-09-23 09:48 UTCGHSA enrichment
  31. 2026-09-23 05:27 UTCGHSA enrichment
  32. 2026-09-23 01:06 UTCGHSA enrichment
  33. 2026-09-22 20:44 UTCEG score recompute
  34. 2026-09-22 20:44 UTCGHSA enrichment
  35. 2026-09-22 12:25 UTCGHSA enrichment
  36. 2026-09-22 07:53 UTCGHSA enrichment
  37. 2026-09-22 03:32 UTCGHSA enrichment
  38. 2026-09-21 23:10 UTCEG score recompute
  39. 2026-09-21 23:10 UTCGHSA enrichment
  40. 2026-09-21 18:48 UTCGHSA enrichment
  41. 2026-09-21 13:56 UTCGHSA enrichment
  42. 2026-09-21 09:04 UTCGHSA enrichment
  43. 2026-09-21 04:16 UTCGHSA enrichment
  44. 2026-09-20 23:55 UTCEG score recompute
  45. 2026-09-20 23:55 UTCGHSA enrichment
  46. 2026-09-20 19:15 UTCGHSA enrichment
  47. 2026-09-20 14:54 UTCGHSA enrichment
  48. 2026-09-20 09:49 UTCGHSA enrichment
  49. 2026-09-20 05:12 UTCGHSA enrichment
  50. 2026-09-20 00:51 UTCGHSA enrichment
  51. 2026-09-19 20:30 UTCGHSA enrichment
  52. 2026-09-19 16:08 UTCEG score recompute
  53. 2026-09-19 16:08 UTCGHSA enrichment
  54. 2026-09-19 11:16 UTCGHSA enrichment
  55. 2026-09-19 06:54 UTCGHSA enrichment
  56. 2026-09-19 02:21 UTCGHSA enrichment
  57. 2026-09-18 21:57 UTCEG score recompute
  58. 2026-09-18 21:57 UTCGHSA enrichment
  59. 2026-09-18 19:27 UTCEPSS rescore
  60. 2026-09-18 16:48 UTCGHSA enrichment
  61. 2026-09-18 11:05 UTCGHSA enrichment
  62. 2026-09-18 06:44 UTCGHSA enrichment
  63. 2026-09-18 02:23 UTCGHSA enrichment
  64. 2026-09-17 22:02 UTCEG score recompute
  65. 2026-09-17 22:02 UTCGHSA enrichment
  66. 2026-09-17 13:14 UTCGHSA enrichment
  67. 2026-09-17 08:07 UTCGHSA enrichment
  68. 2026-09-17 03:46 UTCGHSA enrichment
  69. 2026-09-16 23:13 UTCGHSA enrichment
  70. 2026-09-16 16:05 UTCEG score recompute
  71. 2026-09-16 16:05 UTCGHSA enrichment
  72. 2026-09-16 14:07 UTCEPSS rescore
  73. 2026-09-16 10:47 UTCGHSA enrichment
  74. 2026-09-16 06:12 UTCEG score recompute
  75. 2026-09-16 06:11 UTCGHSA enrichment

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 on August 16, 2026, with the most recent update on August 26, 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 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-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?
No fix for CVE-2026-19349 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-19349 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.