CVE-2026-0560

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

March 29, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 76a54f0df2df (parisneo/lollms)

Fix landed in parisneo/lollms commit 76a54f0df2df — awaiting tagged release

https://github.com/parisneo/lollms/commit/76a54f0df2df8a5b254aa627d487b5dc939a0263

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
lollms1.1.10 ... 2.1.0 (118 versions)2.1.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-02 13:04 UTCOSV refresh
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:21 UTCEPSS rescore
  18. 2026-08-28 21:40 UTCEPSS rescore
  19. 2026-08-27 14:24 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:48 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 47 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 09:50 UTCEG score recompute
  3. 2026-08-16 09:50 UTCGHSA enrichment
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 19:09 UTCGHSA enrichment
  7. 2026-08-14 06:11 UTCEG score recompute
  8. 2026-08-14 06:11 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 20:30 UTCEG score recompute
  11. 2026-08-12 20:30 UTCGHSA enrichment
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 20:41 UTCEG score recompute
  14. 2026-08-11 20:41 UTCGHSA enrichment
  15. 2026-08-11 13:42 UTCEPSS rescore
  16. 2026-08-11 03:41 UTCEG score recompute
  17. 2026-08-11 03:41 UTCGHSA enrichment
  18. 2026-08-10 23:59 UTCEPSS rescore
  19. 2026-08-10 07:08 UTCGHSA enrichment
  20. 2026-08-09 18:26 UTCGHSA enrichment
  21. 2026-08-09 05:45 UTCEG score recompute
  22. 2026-08-09 05:45 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 04:37 UTCEG score recompute
  25. 2026-08-08 04:37 UTCGHSA enrichment
  26. 2026-08-07 15:57 UTCGHSA enrichment
  27. 2026-08-06 18:29 UTCEG score recompute
  28. 2026-08-06 18:29 UTCGHSA enrichment
  29. 2026-08-06 13:46 UTCEPSS rescore
  30. 2026-08-06 00:41 UTCEG score recompute
  31. 2026-08-06 00:41 UTCGHSA enrichment
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-04 15:09 UTCEPSS rescore
  34. 2026-08-04 10:38 UTCEPSS rescore
  35. 2026-08-03 23:01 UTCEG score recompute
  36. 2026-08-03 23:01 UTCGHSA enrichment
  37. 2026-08-03 10:35 UTCEPSS rescore
  38. 2026-08-02 15:06 UTCEG score recompute
  39. 2026-08-02 15:06 UTCGHSA enrichment
  40. 2026-08-02 02:26 UTCEPSS rescore
  41. 2026-08-01 04:15 UTCEPSS rescore
  42. 2026-07-30 16:27 UTCEPSS rescore
  43. 2026-07-30 01:30 UTCEPSS rescore
  44. 2026-07-28 15:36 UTCEPSS rescore
  45. 2026-07-27 14:13 UTCEPSS rescore
  46. 2026-07-27 12:52 UTCEG score recompute
  47. 2026-07-27 12:52 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-0560.yaml
    First seen Jan 1, 2026

    LolLMS < 2.2.0 - Server-Side Request Forgery

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0560?
CVE-2026-0560 is a high vulnerability published on March 29, 2026. 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 downloadimagetotemp() function in backend/routers/files.py fails to validate user-controlled URLs, allowing attackers to make arbitrary…
When was CVE-2026-0560 disclosed?
CVE-2026-0560 was first published in the National Vulnerability Database on March 29, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0560 actively exploited?
CVE-2026-0560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 23.0% of all scored CVEs.
What is the CVSS score of CVE-2026-0560?
CVE-2026-0560 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-0560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0560, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0560

Explore →

Is Your Infrastructure Affected by CVE-2026-0560?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs