A Server-Side Request Forgery (SSRF) vulnerability has been identified in parisneo/lollms versions prior to 2.2.0. This flaw resides within the /api/files/export-content endpoint, allowing attackers to initiate unauthorized HTTP requests. Successful exploitation can lead to access of internal network resources and cloud metadata, posing a significant security risk. Affected versions include those prior to 2.2.0, and a fix is available in version 2.2.0.
The SSRF vulnerability in lollms allows an attacker to craft malicious requests through the /api/files/export-content endpoint. Because the application fails to properly validate user-supplied URLs, the server will forward these requests to arbitrary destinations. This can enable attackers to scan internal ports, access sensitive cloud metadata (e.g., AWS instance IDs, Azure credentials), and potentially interact with internal services that are not directly exposed to the internet. A successful attacker could leverage this access to gather information about the internal network topology, identify other vulnerable systems, or even attempt to execute code through vulnerable internal services. The blast radius extends to any internal resources accessible via HTTP/HTTPS from the lollms server.
CVE-2026-0560 was publicly disclosed on 2026-03-29. There is no indication of active exploitation campaigns at this time. The vulnerability is not currently listed on the CISA KEV catalog. Public proof-of-concept exploits are not widely available, but the SSRF nature of the vulnerability makes it relatively straightforward to develop and deploy. The ease of exploitation, combined with the potential for significant impact, warrants prompt remediation.
Exploit Status
EPSS
0.11% (30% percentile)
CISA SSVC
The primary mitigation for CVE-2026-0560 is to immediately upgrade lollms to version 2.2.0 or later, which includes the necessary validation to prevent SSRF attacks. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) with rules to block suspicious outbound requests originating from the /api/files/export-content endpoint. Specifically, WAF rules should be configured to filter requests to unusual or internal IP address ranges, as well as requests targeting cloud metadata endpoints. Additionally, review and restrict network access to the lollms server, limiting its ability to reach internal resources unnecessarily. After upgrade, confirm by attempting a file export request with a known malicious URL and verifying that it is blocked.
Update the version of parisneo/lollms to version 2.2.0 or higher. This corrects the SSRF vulnerability by properly validating user-controlled URLs in the `/api/files/export-content` endpoint.
Vulnerability analysis and critical alerts directly to your inbox.
CVE-2026-0560 is a Server-Side Request Forgery (SSRF) vulnerability affecting lollms versions prior to 2.2.0, allowing attackers to make unauthorized HTTP requests.
You are affected if you are running lollms version 2.2.0 or earlier. Upgrade to 2.2.0 to mitigate the risk.
Upgrade lollms to version 2.2.0 or later. As a temporary workaround, implement a WAF to block suspicious outbound requests.
There is currently no evidence of active exploitation, but the vulnerability's nature makes it easily exploitable.
Refer to the parisneo/lollms project repository and associated security advisories for the official announcement and details.
CVSS Vector
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Upload your requirements.txt file and we'll tell you instantly if you're affected.