Loading vulnerability…
CVE-2026-0562 is an authorization flaw in parisneo/lollms affecting versions up to 2.2.0. The vulnerability exists in the respond_request() function in backend/routers/friends.py, exposed via the /api/friends/requests/{friendship_id} endpoint. The endpoint fails to verify that the authenticated user is either a participant in the referenced friendship or the intended recipient of the friend request before allowing the request to be accepted or rejected. As a result, any authenticated user who can supply or enumerate a valid friendship_id can perform state-changing actions on other users’ friend requests, constituting an insecure direct object reference (IDOR) caused by incorrect authorization.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
/api/friends/requests/{friendship_id}, especially repeated access to sequential or unrelated friendship IDs, and consider logging and alerting on failed or cross-user authorization attempts. Reducing identifier predictability may raise exploitation difficulty, but it is not a substitute for proper authorization enforcement.Patch, then assume compromise.
respond_request() should enforce object-level authorization by verifying that the authenticated user is authorized to act on the specified friendship_id, specifically that they are the intended recipient or otherwise a legitimate participant in the friendship record before permitting accept/reject operations. Review similar endpoints for missing ownership or participant validation to prevent related IDOR issues.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.