9

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-54157

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. 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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-54157

CVE-2026-54157:

9

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

SSVC / BOD 26-04 ↗

Exploitation pocAutomatable NoTech Impact Total

Select your environment

→SSVCScheduled60 days

Runtime reachability resolves your actual outcome.Book a demo

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@lobehub/lobehub	npm	<= 2.1.56	2.1.57

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is an unauthenticated Server-Side Request Forgery (SSRF) located at the /webapi/proxy endpoint. The analysis of the fixing commit cb8645f65a1cdeb384fc7d962c1e09090a796355 confirms the vulnerability details. The commit's primary change is the complete removal of the src/app/(backend)/webapi/proxy/route.ts file, which contained the vulnerable code.

The main vulnerable function is the POST handler within this file. It served as the public API endpoint that accepted a URL from a POST request body. This URL was then passed to the ssrfSafeFetch function to be fetched by the server. The critical flaw was the absence of any authentication or authorization check, allowing any individual to use this endpoint as an open proxy. This could be abused for various malicious purposes, including scanning internal networks, accessing cloud provider metadata, or launching attacks against other services from the LobeHub server's IP address.

During exploitation, the POST function would be the entry point, and ssrfSafeFetch would be visible in the execution stack as it performs the outbound request. Other functions like fetchPricing were identified as consumers of this vulnerable proxy from the client-side, which were also patched to remove their dependency on the proxy.

Vulnerable functions

POST

src/app/(backend)/webapi/proxy/route.ts

This function is the unauthenticated API route handler for `POST /webapi/proxy`. It directly processes attacker-controlled input (a URL from the request body) and passes it to `ssrfSafeFetch` to make a server-side request. The lack of an authentication check before processing the request is the root cause of the SSRF vulnerability. The fix was to remove this route entirely.

ssrfSafeFetch

src/app/(backend)/webapi/proxy/route.ts

This function is directly called by the vulnerable `POST` handler to execute the server-side request to the URL provided by the attacker. While the function name suggests it has safety features, it is the component that performs the request action at the heart of the SSRF vulnerability. It would appear in any runtime profile or stack trace during exploitation.

fetchPricing

packages/model-runtime/src/providers/newapi/index.ts

In the browser environment, this function previously used the vulnerable `/webapi/proxy` endpoint to bypass CORS when fetching pricing information. This indicates it was a client-side consumer of the vulnerable proxy. The patch removes the call to the proxy and makes a direct request.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.