Unauthenticated SSRF via missing proxy authentication
Published Jun 23, 2026 · Updated Jun 23, 2026
SSRF in LobeHub before 2.1.57 allows remote attackers to make server-side outbound requests through the unauthenticated proxy endpoint. In src/app/(backend)/webapi/proxy/route.ts, POST reads a body-supplied URL and passes it to ssrfSafeFetch() without checkAuth(), while middleware skips /webapi/. No account is required; responses reflect upstream bodies and headers, exposing deployment details and enabling lobehub.com cookie injection.
Summary
What happened
SSRF in LobeHub before 2.1.57 allows remote attackers to make server-side outbound requests through the unauthenticated proxy endpoint. In src/app/(backend)/webapi/proxy/route.ts, POST reads a body-supplied URL and passes it to ssrfSafeFetch() without checkAuth(), while middleware skips /webapi/. No account is required; responses reflect upstream bodies and headers, exposing deployment details and enabling lobehub.com cookie injection.
The record
- CVE
- CVE-2026-54157
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- LobeHub
- Product
- LobeHub
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.57
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream /webapi/proxy curl reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo