PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-59095 lobehub CVE debrief

CVE-2026-59095 is a high-severity server-side request forgery vulnerability in LobeChat before 2.2.10-canary.18. Authenticated attackers can exploit this to direct internal HTTP requests to arbitrary URLs, potentially disclosing internal service responses and cloud credentials. The vulnerability exists in the skill import service (importFromUrl) and topic cover update (fetchImageFromUrl) endpoints of LobeChat. These endpoints use the global fetch without the project's ssrf-safe-fetch wrapper, allowing attackers to target internal addresses such as cloud instance metadata endpoints. Users of LobeChat versions prior to 2.2.10-canary.18 should apply the patch or upgrade to a secure version. Security teams should review and monitor LobeChat instances for potential exploitation.

Vendor
lobehub
Product
Unknown
CVSS
HIGH 8.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-02
Original CVE updated
2026-07-07
Advisory published
2026-07-02
Advisory updated
2026-07-07

Who should care

Users of LobeChat versions prior to 2.2.10-canary.18, security teams responsible for monitoring and protecting LobeChat instances, and operators of LobeChat in managed environments should apply the patch or upgrade to a secure version. Security teams should review and monitor LobeChat instances for potential exploitation and check LobeChat logs for suspicious activity.

Technical summary

The vulnerability exists in the skill import service (importFromUrl) and topic cover update (fetchImageFromUrl) endpoints of LobeChat. These endpoints use the global fetch without the project's ssrf-safe-fetch wrapper, allowing attackers to target internal addresses such as cloud instance metadata endpoints. Attackers can exploit this vulnerability to direct internal HTTP requests to arbitrary URLs, potentially disclosing internal service responses and cloud credentials. The affected product is LobeChat, and the vulnerability is classified as a server-side request forgery (SSRF) vulnerability.

Defensive priority

High priority should be given to patching or upgrading LobeChat instances. Security teams should monitor for potential exploitation and review LobeChat logs for suspicious activity.

Recommended defensive actions

  • Apply the patch or upgrade to LobeChat version 2.2.10-canary.18 or later
  • Review and monitor LobeChat instances for potential exploitation
  • Check LobeChat logs for suspicious activity
  • Implement additional security measures to protect internal services
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-02T20:17:07.673Z and last modified on 2026-07-07T18:16:40.023Z. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The skill import service (importFromUrl) and topic cover update (fetchImageFromUrl) endpoints are reportedly vulnerable, but additional details are needed to fully understand the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-59095 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-59095

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-59095 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-59095

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.