Quick answers
- Is CVE-2026-1163 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-1163 being exploited in the wild.
- How severe is CVE-2026-1163?
- Medium severity, with a CVSS score of 4.1, published 8 April 2026.
- Which products and versions are affected?
- lollms (PyPI) ECOSYSTEM:introduced=0,last_affected=11.0.0.
- Is there a fix for CVE-2026-1163?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-1163 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-1163?
- Check whether you run lollms (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is classified as CWE-613 (Insufficient Session Expiration) within the parisneo/lollms application. The root cause is a failure to invalidate existing session tokens upon a password reset event, combined with a lack of inactivity-based session termination and an excessively long default session lifespan of 31 days. An attacker who has already obtained a valid session token can maintain persistent access to the compromised account even after the victim changes their credentials. The attack requires the attacker to already possess high-privileged session access, resulting in a CVSS score of 4.1.
Affected products
- parisneo lollms (Lord of Large Language Models) latest version (as of April 2026)
Identifiers
- CVE-2026-1163
- GHSA-8jg2-726g-xh43
- PYSEC-2026-2612
Timeline
- 2026-04-08: advisory: NVD published the CVE record based on a huntr.dev report.