# CVE-2026-1163: Insufficient Session Expiration in parisneo/lollms

> Attackers can maintain persistent access to compromised accounts after password resets due to insufficient session expiration in lollms.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8jg2-726g-xh43, PYSEC-2026-2612

## What is CVE-2026-1163?

CVE-2026-1163 is a medium-severity authentication bypass vulnerability in parisneo/lollms, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An insufficient session expiration vulnerability exists in the latest version of parisneo/lollms. The application fails to invalidate active sessions after a password reset, allowing an attacker to continue using an old session token. This issue arises due to the absence of logic to reject requests after a period of inactivity and the excessively long default session duration of 31 days. The vulnerability enables an attacker to maintain persistent access to a compromised account, even after the victim resets their password.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-1163?

3 open source packages ship an affected version, including lollms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lollms` | PyPI | All versions to 11.0.0 | None |
| `lollms` | PyPI | All versions to 11.0.0 | None |
| `lollms` | PyPI | All versions to 11.0.0 | None |

## How do I fix CVE-2026-1163?

No fix has been published for CVE-2026-1163 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1163 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1163 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1163 and fix it if it is affected.

What it is: CVE-2026-1163 is a medium-severity authentication bypass vulnerability in parisneo/lollms, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1163 exists.

Affected packages and fixed versions:
- lollms (PyPI): affected all versions up to 11.0.0; no fix listed
- lollms (PyPI): affected all versions up to 11.0.0; no fix listed
- lollms (PyPI): affected all versions up to 11.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1163/ (Markdown: https://insights.sbomify.com/CVE-2026-1163/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1163
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1163
- OSV: https://osv.dev/vulnerability/CVE-2026-1163

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1163/
Summaries are generated and may contain mistakes; the official description above is the record.