Security Digest · Vulnerability record

CVE-2026-54157: LobeHub: Unauthenticated SSRF in `/webapi/proxy`

LobeHub is a work-and-lifestyle space to find, build, and collaborate with agent teammates that grow with you.

CVSS 9.0 Critical EPSS 1.8% · p79

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 1.8%, percentile 79: FIRST’s model estimates a 1.8% chance of exploitation activity in the next 30 days, higher than 79% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Needs an account (high (admin)). Exposure depends on who can log in.
  • Only applies if your dependency tree includes @lobehub/lobehub (npm) <= 2.1.56, fixed in 2.1.57. Check your lockfile, including transitive dependencies.

What it is

LobeHub is a work-and-lifestyle space to find, build, and collaborate with agent teammates that grow with you. Prior to 2.1.57, the /webapi/proxy endpoint on app.lobehub.com accepts a URL in the POST body and fetches it server-side without any authentication. An attacker can use this to make arbitrary outbound requests from LobeHub's infrastructure, leak Vercel deployment details, and inject cookies on the lobehub.com domain through reflected Set-Cookie headers. This vulnerability is fixed in 2.1.57.

From the GitHub advisory

Unauthenticated SSRF in /webapi/proxy allows anyone to proxy requests and inject cookies on lobehub.com

Summary

The /webapi/proxy endpoint on app.lobehub.com accepts a URL in the POST body and fetches it server-side without any authentication. This is the same proxy code that was vulnerable in CVE-2024-32964, where /api/proxy was fixed by adding auth middleware. The /webapi/proxy route was never secured — it is the only webapi route missing the checkAuth() wrapper. An attacker can use this to make arbitrary outbound requests from LobeHub's infrastructure, leak Vercel deployment details, and inject cookies on the lobehub.com domain through reflected Set-Cookie headers.

Vulnerability Details

Type: Server-Side Request Forgery (CWE-918) Affected Endpoint: POST /webapi/proxy Vulnerable File: src/app/(backend)/webapi/proxy/route.ts

Weakness type: CWE-918.

Product: @lobehub/lobehub (npm) · Assigned by: GitHub_M · Published: 2026-06-23

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npm@lobehub/lobehub<= 2.1.562.1.57
VendorProductAffected versions (per CVE record)
lobehublobehub< 2.1.57

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19 CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:H
GitHub3.19.0 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: high (admin)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 1.83% probability of exploitation activity in the next 30 days; percentile 79.

Timeline

  • — GitHub-reviewed advisory GHSA-xmwj-c75x-6346 published (critical)
  • — CVE record last updated
  • — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-xmwj-c75x-6346 github.com
  2. CVE.org record CVE-2026-54157 cve.org
  3. NVD entry CVE-2026-54157 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com

Critical npm advisories · Today’s Security Digest