CVE-2026-54157
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLobeHub 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe /webapi/proxy endpoint on app.lobehub.com accepts a URL in the POST body and fetches it server-side without any authentication, enabling Server-Side Request Forgery (SSRF). Attackers can leverage this to make arbitrary outbound requests from the infrastructure, leak Vercel deployment details, and inject cookies on the lobehub.com domain through reflected Set-Cookie headers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LobeHub installation and versionLocate the LobeHub application in your environment and determine the installed version by checking package.json, Docker image tag, or the application's /api/version or /about endpoint. Compare against version 2.1.57.Affected if The installed version is below 2.1.57 or cannot be determined to be 2.1.57 or later.
-
Locate the /webapi/proxy endpointCheck if the /webapi/proxy endpoint exists in your LobeHub deployment by reviewing the application routing configuration, API route files, or attempting to access the endpoint at your deployment base URL.Affected if The /webapi/proxy endpoint exists in the application routes.
-
Test endpoint accessibility and authenticationSend a POST request to /webapi/proxy with a JSON body containing a 'url' field (e.g., {"url":"http://example.com"}) without including any authentication headers or tokens. Observe whether the server attempts to fetch the provided URL.Affected if The endpoint accepts the request without requiring authentication and attempts to fetch the attacker-controlled URL.
-
Check for network isolation or WAF rulesReview network configuration, firewall rules, or Web Application Firewall settings that may restrict outbound requests from the application server, or verify if the proxy endpoint has any rate limiting or input validation applied.Affected if No network restrictions or input validation exists, and the endpoint accepts arbitrary URLs.
Your environment is affected if you are running LobeHub version below 2.1.57 with the /webapi/proxy endpoint exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to LobeHub version 2.1.57 or later. Until patched, disable or restrict access to the /webapi/proxy endpoint and implement proper authentication and input validation for any proxy functionality.
2.1.57
- 1. Upgrade LobeHub to version 2.1.57 or later to remediate the SSRF vulnerability in the /webapi/proxy endpoint.
- 2. If using a package manager, update the LobeHub package to the latest version that includes the fix.
- 3. If using a containerized deployment, pull the updated container image tagged with version 2.1.57 or later.
- 4. After upgrading, verify that the /webapi/proxy endpoint now requires authentication or has been properly secured.
- 5. Review server logs for any signs of exploitation attempts prior to the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54157 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data