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

Critical 9.0 Published Updated

Unauthenticated attackers can exploit an SSRF vulnerability in LobeHub to make arbitrary server-side requests and leak sensitive deployment details.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-54157?

CVE-2026-54157 is a critical server-side request forgery vulnerability in lobehub, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

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.

Weakness: CWE-918

Which versions are affected by CVE-2026-54157?

2 open source packages ship an affected version, including @lobehub/lobehub.

PackageAffectedFixed in
@lobehub/lobehub npmAll versions2.1.57
@lobehub/lobehub npmAll versions2.1.57

How do I fix CVE-2026-54157?

Upgrade @lobehub/lobehub to 2.1.57 or later.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-54157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54157 exists.

Public exploit code: 1 Nuclei template.

Sources

Also known as GHSA-xmwj-c75x-6346.

Is CVE-2026-54157 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free