Which products and versions are affected by CVE-2026-54157?

Affected: @lobehub/lobehub (npm); lobehub. The full list is in the CVE brief.

Is CVE-2026-54157 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-54157 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-54157?

Public exploit code is available.

Is there a fix for CVE-2026-54157?

Fixed versions are available, including @lobehub/lobehub 2.1.57, lobehub 2.1.57.

How urgently should CVE-2026-54157 be patched?

Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Request A Demo

Vulnerability Intelligence

CVE-2026-54157

CriticalPublic exploit

LobeHub: Unauthenticated SSRF in /webapi/proxy

Published Jun 16, 2026 · Updated Sep 25, 2026 · Also known as EUVD-2026-38555, GHSA-xmwj-c75x-6346

Key Facts

Patch immediately

CVE-2026-54157 is a critical-severity vulnerability (CVSS 9.0 v3.1) affecting @lobehub/lobehub (npm), lobehub.
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 1.8% probability of exploitation in the next 30 days.
Fixed versions are available, including @lobehub/lobehub 2.1.57, lobehub 2.1.57.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

CVSS v3.1

9.0

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:H

EPSS (30-day exploit likelihood)

1.8%

Higher than 78.5% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2026-54157 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

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.

Affected Products

2 affected entries in total

Product	Affected versions	Fixed in
@lobehub/lobehubnpm	See advisory	2.1.57
lobehub	See advisory	2.1.57

Patched Releases

@lobehub/lobehub

2.1.57

lobehub

2.1.57

Timeline

Publicly disclosed
Jun 16, 2026
Last updated
Sep 25, 2026

Weakness Type

CWE-918 Server-Side Request Forgery (SSRF)

References

FAQ

Common Questions.

LobeHub is a work-and-lifestyle space to find, build, and collaborate with agent teammates that grow with you.
Affected: @lobehub/lobehub (npm); lobehub. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including @lobehub/lobehub 2.1.57, lobehub 2.1.57.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Is CVE-2026-54157 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.