dbcve.org
LollmsApplication

CVE-2026-0558

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to after 2.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 not enforce authentication, unlike other file-related endpoints, and lacks the `Depends(get_current_active_user)` dependency. This issue can lead to denial of service (DoS) through resource exhaustion, information disclosure, and violation of the application's documented security policies.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /api/files/extract-text endpoint in parisneo/lollms up to v2.2.0 lacks authentication enforcement, missing the Depends(get_current_active_user) dependency present on other file endpoints. This allows unauthenticated users to upload and process files, enabling resource exhaustion DoS attacks and potential information disclosure.

MitigationAdd the Depends(get_current_active_user) authentication dependency to the /api/files/extract-text endpoint to enforce authentication consistent with other file-related endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LollmsApplication
Affected:<= 2.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Lollms version
    Identify the installed version of parisneo/lollms (e.g., check package.json, docker image tag, or application metadata) and compare it to the affected range: <= 2.1.0
    Affected if The installed version is 2.1.0 or earlier, or any version up to and including 2.2.0
  2. Verify the /api/files/extract-text endpoint exists
    Confirm that the Lollms instance exposes the /api/files/extract-text API endpoint (check API documentation, route definitions, or attempt a request to the endpoint)
    Affected if The endpoint is exposed and accessible in the environment
  3. Test endpoint authentication requirement
    Send an unauthenticated HTTP request to /api/files/extract-text (or the full path such as /api/files/extract-text) without providing valid authentication credentials (no Bearer token, session cookie, or API key) and observe the response
    Affected if The endpoint accepts the request and returns a successful response (200 OK) instead of returning a 401 Unauthorized or 403 Forbidden error, indicating authentication is not enforced
  4. Compare authentication on similar file endpoints
    Send unauthenticated requests to other file-related endpoints (such as /api/files/upload, /api/files/list, or similar) and verify they properly require authentication (expect 401/403 responses)
    Affected if Other file endpoints correctly reject unauthenticated requests but /api/files/extract-text does not, confirming the missing Depends(get_current_active_user) dependency

A user is affected if running Lollms version 2.1.0 or earlier (or any version up to 2.2.0) and the /api/files/extract-text endpoint accepts unauthenticated requests while other file endpoints properly enforce authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.1.0
Vendor patch github.com →
Interim mitigation

Add the Depends(get_current_active_user) authentication dependency to the /api/files/extract-text endpoint to enforce authentication consistent with other file-related endpoints.

Recommended fix High confidence

Lollms version 2.2.1 or later

  1. 1. Back up your current Lollms installation and any important data
  2. 2. Review the vendor fix at commit a6625dc83786ff21d109b0d545ca61b770607ef3 which adds Depends(get_current_active_user) to the /api/files/extract-text endpoint
  3. 3. Upgrade Lollms to a version that includes this fix (version 2.2.1 or later)
  4. 4. After upgrade, verify the /api/files/extract-text endpoint now requires authentication by attempting an unauthenticated request
  5. 5. Confirm other file-related endpoints continue to function with proper authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lollms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0558 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data