Vulnerability in lemur (CVE-2026-44305)
Summary
Vulnerability in lemur (CVE-2026-44305). Confidential information can be exposed externally. Exploitable via ldap. Mitigation: upgrade to 1.9.0 or later.
Original description
The description as published by the source.
Lemur manages TLS certificate creation. Prior to 1.9.0, when LDAP TLS is enabled (LDAP_USE_TLS = True), Lemur's LDAP authentication module unconditionally disables TLS certificate verification at the global ldap module level. This allows a man-in-the-middle attacker positioned between Lemur and the LDAP server to intercept all authentication credentials. This vulnerability is fixed in 1.9.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44305 has been found in lemur.
Attackers can target a specific entry point like ldap over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade lemur to 1.9.0 or later.
If unsure, ask your IT team or search "lemur CVE-2026-44305" on the vendor's site.
CVE-2026-44305 (lemur) — CWE-295 / CVSS v3 6.8
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: ldap / OPT_X_TLS_NEVER / mitmproxy / stunnel
Patched: 1.9.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-295) exists in lemur. Attackers reach the vulnerable code path via ldap without authentication.
Check the vendor advisory for the affected versions of lemur. Attack surface: ldap / OPT_X_TLS_NEVER / mitmproxy / stunnel.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 1.9.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'lemur' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'lemur' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
lemurを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade lemur to 1.9.0ステージング環境で 1.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web python-ldap.org
- web github.com