# A vulnerability in parisneo/lollms, up to and including version 2.2.0, allows unauthenticated users to upload and process files through the \`/api/files/extract-text\` endpoint. This endpoint does no...

Advisory record · `PYSEC-2026-2198`

- **Identifiers:** `PYSEC-2026-2198` · `CVE-2026-0558`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 29 Mar 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by OSV at 29 Mar 2026, 18:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `lollms` (PyPI): affected `<2.1.1`; fixed in `2.1.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> lollms versions before 2.1.1 (the description says up to and including 2.2.0) have a file text-extraction endpoint that does not require authentication. An unauthenticated attacker can upload and process files, causing possible denial of service and information disclosure. Upgrade lollms to 2.1.1 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 82nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-2198)

## Sources

- [OSV: PYSEC-2026-2198](https://osv.dev/vulnerability/PYSEC-2026-2198)
- <https://github.com/parisneo/lollms/commit/a6625dc83786ff21d109b0d545ca61b770607ef3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-2198>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-2198/>. Everything for agents: <https://agentprime.io/llms.txt>.
