# CVE-2026-0562: Insecure Direct Object Reference (IDOR) in parisneo/lollms

> Authenticated users can accept or reject friend requests belonging to other users due to missing authorization checks in the API endpoint.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Mar 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-2j48-mfm5-x2hv, PYSEC-2026-204

## What is CVE-2026-0562?

CVE-2026-0562 is a high-severity missing authorization vulnerability in parisneo/lollms, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A critical security vulnerability in parisneo/lollms versions up to 2.2.0 allows any authenticated user to accept or reject friend requests belonging to other users. The `respond_request()` function in `backend/routers/friends.py` does not implement proper authorization checks, enabling Insecure Direct Object Reference (IDOR) attacks. Specifically, the `/api/friends/requests/{friendship_id}` endpoint fails to verify whether the authenticated user is part of the friendship or the intended recipient of the request. This vulnerability can lead to unauthorized access, privacy violations, and potential social engineering attacks. The issue has been addressed in version 2.2.0.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including lollms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lollms` | PyPI | All versions | 2.1.1 |

Products: Lollms Lollms.

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

Upgrade lollms to 2.1.1 or later.

## Is CVE-2026-0562 being exploited?

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

## Other vulnerabilities in parisneo/lollms

- [CVE-2026-1114](https://insights.sbomify.com/CVE-2026-1114/): Improper Access Control via Weak JWT Token in parisneo/lollms (critical 9.8)
- [CVE-2024-3429](https://insights.sbomify.com/CVE-2024-3429/): Path Traversal in parisneo/lollms (critical 9.8)
- [CVE-2026-1115](https://insights.sbomify.com/CVE-2026-1115/): Stored XSS in parisneo/lollms (critical 9.6)
- [CVE-2026-12228](https://insights.sbomify.com/CVE-2026-12228/): Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms (high 8.7)
- [CVE-2026-1116](https://insights.sbomify.com/CVE-2026-1116/): Cross-site Scripting (XSS) in parisneo/lollms (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0562 is a high-severity missing authorization vulnerability in parisneo/lollms, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0562 exists.

Affected packages and fixed versions:
- lollms (PyPI): affected all versions; fixed in 2.1.1

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-0562/ (Markdown: https://insights.sbomify.com/CVE-2026-0562/index.md)
```

## Sources

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

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