CVE-2026-59095

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

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

LobeChat before 2.2.10-canary.18 contains a server-side request forgery vulnerability that allows authenticated attackers to direct internal HTTP requests to arbitrary URLs by supplying user-controlled input to the skill import service (importFromUrl) and topic cover update (fetchImageFromUrl) endpoints, which use the global fetch without the project's ssrf-safe-fetch wrapper. Attackers can target internal addresses such as cloud instance metadata endpoints through these unprotected code paths to disclose internal service responses and cloud credentials.

CVSS v3
7.7
EG Score
7.7(high)
EPSS
14.5%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

LobeHub < 2.2.10-canary.18 - SSRF via importFromUrl and fetchImageFromUrl | Advisories | VulnCheck

https://www.vulncheck.com/advisories/lobechat-canary-18-ssrf-via-importfromurl-and-fetchimagefromurl
github_pr

🔒 fix(skill): route user-supplied URL fetches through ssrfSafeFetch (SSRF, #16536)

Fix merged in lobehub/lobehub PR #16601 on 2026-07-02 — awaiting tagged release

https://github.com/lobehub/lobehub/pull/16601
generic

Authenticated SSRF via raw fetch bypassing ssrf-safe-fetch (skill import and generation cover) · Issue #16536 · lobehub/lobehub · GitHub

https://github.com/lobehub/lobehub/issues/16536

Vendor Advisories for CVE-2026-59095(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 29× 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-07-07 00:15 UTCEG score recompute
  2. 2026-07-07 00:15 UTCGHSA enrichment
  3. 2026-07-06 19:18 UTCNVD updateCVSS v4 → 8.3
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 13:22 UTCEG score recompute
  7. 2026-07-06 13:22 UTCGHSA enrichment
  8. 2026-07-06 02:29 UTCEG score recompute
  9. 2026-07-06 02:29 UTCGHSA enrichment
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 15:36 UTCEG score recompute
  13. 2026-07-05 15:36 UTCGHSA enrichment
  14. 2026-07-05 04:43 UTCEG score recompute
  15. 2026-07-05 04:43 UTCGHSA enrichment
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 17:41 UTCEG score recompute
  19. 2026-07-04 17:41 UTCGHSA enrichment
  20. 2026-07-04 06:49 UTCEG score recompute
  21. 2026-07-04 06:48 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-03 19:53 UTCEG score recompute
  25. 2026-07-03 19:53 UTCGHSA enrichment
Show 4 more
  1. 2026-07-03 09:00 UTCEG score recompute
  2. 2026-07-03 09:00 UTCGHSA enrichment
  3. 2026-07-02 22:06 UTCEG score recompute
  4. 2026-07-02 22:06 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59095?
CVE-2026-59095 is a high vulnerability published on July 2, 2026. LobeChat before 2.2.10-canary.18 contains a server-side request forgery vulnerability that allows authenticated attackers to direct internal HTTP requests to arbitrary URLs by supplying user-controlled input to the skill import service (importFromUrl) and topic cover update (fetchImageFromUrl)…
When was CVE-2026-59095 disclosed?
CVE-2026-59095 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59095 actively exploited?
CVE-2026-59095 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59095?
CVE-2026-59095 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-59095?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59095, 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

Explore the affected products and dependency analysis for CVE-2026-59095

Explore →

Is Your Infrastructure Affected by CVE-2026-59095?

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

Start Free Scan →Browse All CVEs