What is the CVSS score of CVE-2026-0560?

CVE-2026-0560 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of Lollms are affected by CVE-2026-0560?

An unauthenticated Server-Side Request Forgery (SSRF) vulnerability in LoLLMs versions before 2.2.0 allows attackers to make arbitrary HTTP requests from your server to internal networks and cloud…. A patch is available.

Is there a public PoC exploit available for CVE-2026-0560?

Yes, a public proof-of-concept exploit is available for CVE-2026-0560. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-0560?

Within 24 hours: Identify all instances of LoLLMs running versions prior to 2.2.0 using inventory or endpoint detection tools; prioritize production systems. Within 7 days: Upgrade all affected LoLLMs instances to version 2.2.0 or later (patch available in commit 76a54f0); apply WAF rules to block requests to `/api/files/export-content` endpoint from untrusted networks pending patching. Within 30 days: Conduct network segmentation audit to restrict server egress to internal services; implement API authentication and URL allowlist validation for HTTP request functions; review logs for exploitation attempts against the vulnerable endpoint.

Lollms CVE-2026-0560

EUVD-2026-17037 HIGH

Server-Side Request Forgery (SSRF) (CWE-918)

2026-03-29 security@huntr.dev

RCE Information Disclosure SSRF Lollms

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:11 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2.2.0

EUVD ID Assigned

Mar 29, 2026 - 18:22 euvd

EUVD-2026-17037

Analysis Generated

Mar 29, 2026 - 18:22 vuln.today

CVE Published

Mar 29, 2026 - 18:16 nvd

HIGH 7.5

DescriptionCVE.org

A Server-Side Request Forgery (SSRF) vulnerability exists in parisneo/lollms versions prior to 2.2.0, specifically in the /api/files/export-content endpoint. The _download_image_to_temp() function in backend/routers/files.py fails to validate user-controlled URLs, allowing attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints. This vulnerability can lead to internal network access, cloud metadata access, information disclosure, port scanning, and potentially remote code execution.

AnalysisAI

Server-Side Request Forgery (SSRF) in parisneo/lollms versions before 2.2.0 allows unauthenticated remote attackers to make arbitrary HTTP requests to internal services and cloud metadata endpoints via the /api/files/export-content endpoint. The vulnerability stems from insufficient URL validation in the _download_image_to_temp() function, enabling internal network reconnaissance, access to cloud instance metadata (AWS/GCP/Azure), and potential remote code execution through server-side exploitation chains. EPSS data not available; no public exploit identified at time of analysis. Vendor-released patch available in commit 76a54f0 and version 2.2.0.

Technical ContextAI

The vulnerability affects the lollms (Lord of Large Language Models) framework, a Python-based application for managing large language models. The flaw resides in the /api/files/export-content API endpoint within the backend/routers/files.py file, specifically in the _download_image_to_temp() function. This function accepts user-controlled URLs without proper validation or allowlist enforcement, allowing manipulation to target arbitrary internal endpoints. CWE-918 (Server-Side Request Forgery) represents a failure to restrict URL schemes, hostnames, or ports before making server-initiated HTTP requests. In cloud environments, SSRF commonly targets metadata services at 169.254.169.254 (AWS/Azure) or metadata.google.internal (GCP) to extract IAM credentials, API keys, and instance configuration data. The CVSS vector AV:N indicates network-accessible attack surface, AC:L confirms low complexity requiring no specialized conditions, and PR:N confirms no authentication barrier.

RemediationAI

Immediately upgrade to lollms version 2.2.0 or later, which includes commit 76a54f0df2df8a5b254aa627d487b5dc939a0263 that implements proper URL validation in the _download_image_to_temp() function. Organizations unable to upgrade immediately should implement network-level controls to restrict outbound HTTP requests from the lollms application server, blocking access to RFC1918 private address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback addresses (127.0.0.0/8), link-local addresses (169.254.0.0/16), and cloud metadata endpoints. Additional mitigation includes deploying a web application firewall (WAF) to filter requests to /api/files/export-content containing suspicious URL patterns, and implementing strict egress firewall rules to prevent SSRF exploitation. In cloud environments, ensure Instance Metadata Service version 2 (IMDSv2) is enforced on AWS EC2 instances to require session tokens for metadata access. Review application logs for suspicious activity targeting the vulnerable endpoint prior to patching. Full technical details and patch implementation are available in the huntr.com disclosure at https://huntr.com/bounties/65e43a5e-b902-4369-b738-1825285a3ea5.