← Back
CVE-2026-1117
Vulnerability in lollms (CVE-2026-1117)
Summary
vulnerability in lollms (CVE-2026-1117). Risk of unauthorized operations or information disclosure. Exploitable via ``lollms_generation_events.py``. Mitigation: upgrade to `2.1.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-1117** has been found in lollms.
Attackers can target a specific entry point like ``lollms_generation_events.py`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade lollms to **2.1.0** or later.
If unsure, ask your IT team or search "lollms CVE-2026-1117" on the vendor's site.
CVE-2026-1117 (lollms) — CWE-284 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `lollms_generation_events.py` / `add_events` / `generate_text` / `cancel_generation`
Patched: `2.1.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.
❓ What is the problem
**A vulnerability** (CWE-284) exists in lollms. Attackers reach the vulnerable code path via ``lollms_generation_events.py`` without authentication.
📍 Affected scope
lollms — . Attack surface: `lollms_generation_events.py` / `add_events` / `generate_text` / `cancel_generation`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.1.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'lollms' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'lollms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `lollms` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade lollms to 2.1.0ステージング環境で 2.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
lollms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-1117
- advisory https://github.com/advisories/GHSA-82fw-ch24-j34w
- package https://github.com/parisneo/lollms
- package https://pypi.org/project/lollms
- web https://github.com/parisneo/lollms/commit/36a5b513dfefe9c2913bf9b618457b4fea603e3b
- web https://huntr.com/bounties/d2846a7f-0140-4105-b1bb-5ef64ec8b829