CVE-2026-54157

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.8%, top 24% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.0
EG Score
9.0(medium)
EPSS
75.6%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Unauthenticated SSRF in `/webapi/proxy` · Advisory · lobehub/lobehub · GitHub

https://github.com/lobehub/lobehub/security/advisories/GHSA-xmwj-c75x-6346

Vendor Advisories for CVE-2026-54157(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@lobehub/lobehub—2.1.57—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 43× in last 7d / 128× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-07-07 03:13 UTCEG score recompute
  2. 2026-07-06 23:03 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 05:35 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 01:26 UTCEG score recompute
  9. 2026-07-05 21:16 UTCEG score recompute
  10. 2026-07-05 17:07 UTCEG score recompute
  11. 2026-07-05 12:57 UTCEG score recompute
  12. 2026-07-05 08:42 UTCEG score recompute
  13. 2026-07-05 02:51 UTCEG score recompute
  14. 2026-07-05 02:31 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 22:42 UTCEG score recompute
  17. 2026-07-04 18:31 UTCEG score recompute
  18. 2026-07-04 13:15 UTCEG score recompute
  19. 2026-07-04 09:06 UTCEG score recompute
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-03 22:41 UTCEG score recompute
  23. 2026-07-03 18:23 UTCEG score recompute
  24. 2026-07-03 13:46 UTCEG score recompute
  25. 2026-07-03 07:06 UTCEG score recompute
Show 75 more
  1. 2026-07-03 02:51 UTCEG score recompute
  2. 2026-07-02 22:41 UTCEG score recompute
  3. 2026-07-02 18:30 UTCEG score recompute
  4. 2026-07-02 14:20 UTCEG score recompute
  5. 2026-07-02 10:11 UTCEG score recompute
  6. 2026-07-02 06:01 UTCEG score recompute
  7. 2026-07-02 01:50 UTCEG score recompute
  8. 2026-07-01 21:40 UTCEG score recompute
  9. 2026-07-01 17:31 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 13:20 UTCEG score recompute
  12. 2026-07-01 09:08 UTCEG score recompute
  13. 2026-07-01 04:59 UTCEG score recompute
  14. 2026-07-01 00:37 UTCEG score recompute
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 20:28 UTCEG score recompute
  17. 2026-06-30 16:18 UTCEG score recompute
  18. 2026-06-30 12:10 UTCEG score recompute
  19. 2026-06-30 07:15 UTCEG score recompute
  20. 2026-06-30 03:06 UTCEG score recompute
  21. 2026-06-29 22:56 UTCEG score recompute
  22. 2026-06-29 18:48 UTCEG score recompute
  23. 2026-06-29 14:38 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 10:29 UTCEG score recompute
  27. 2026-06-29 06:20 UTCEG score recompute
  28. 2026-06-29 02:09 UTCEG score recompute
  29. 2026-06-28 22:00 UTCEG score recompute
  30. 2026-06-28 17:51 UTCEG score recompute
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 13:41 UTCEG score recompute
  33. 2026-06-28 09:31 UTCEG score recompute
  34. 2026-06-28 05:22 UTCEG score recompute
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 01:14 UTCEG score recompute
  38. 2026-06-27 21:05 UTCEG score recompute
  39. 2026-06-27 16:55 UTCEG score recompute
  40. 2026-06-27 12:44 UTCEG score recompute
  41. 2026-06-27 08:35 UTCEG score recompute
  42. 2026-06-27 04:26 UTCEG score recompute
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-27 00:16 UTCEG score recompute
  45. 2026-06-26 20:07 UTCEG score recompute
  46. 2026-06-26 15:58 UTCEG score recompute
  47. 2026-06-26 11:50 UTCEG score recompute
  48. 2026-06-26 05:23 UTCEG score recompute
  49. 2026-06-26 01:15 UTCEG score recompute
  50. 2026-06-25 21:06 UTCEG score recompute
  51. 2026-06-25 16:55 UTCEG score recompute
  52. 2026-06-25 13:49 UTCEPSS rescore
  53. 2026-06-25 12:46 UTCEG score recompute
  54. 2026-06-25 08:37 UTCEG score recompute
  55. 2026-06-25 04:28 UTCEG score recompute
  56. 2026-06-25 00:12 UTCEG score recompute
  57. 2026-06-24 19:58 UTCEG score recompute
  58. 2026-06-24 15:13 UTCEG score recompute
  59. 2026-06-24 14:05 UTCEPSS rescore
  60. 2026-06-24 11:04 UTCEG score recompute
  61. 2026-06-24 06:53 UTCEG score recompute
  62. 2026-06-24 02:44 UTCEG score recompute
  63. 2026-06-23 22:35 UTCEG score recompute
  64. 2026-06-23 18:25 UTCEG score recompute
  65. 2026-06-23 14:16 UTCEG score recompute
  66. 2026-06-23 09:58 UTCEG score recompute
  67. 2026-06-23 05:48 UTCEG score recompute
  68. 2026-06-23 01:23 UTCEG score recompute
  69. 2026-06-22 21:14 UTCEG score recompute
  70. 2026-06-22 17:01 UTCEG score recompute
  71. 2026-06-22 12:08 UTCEG score recompute
  72. 2026-06-22 07:40 UTCEG score recompute
  73. 2026-06-22 03:24 UTCEG score recompute
  74. 2026-06-21 22:38 UTCEG score recompute
  75. 2026-06-21 18:20 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-54157.yaml
    First seen Jan 1, 2026

    LobeHub LobeChat <= 2.1.56 - Server-Side Request Forgery

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54157?
CVE-2026-54157 is a critical vulnerability published on June 16, 2026. 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…
When was CVE-2026-54157 disclosed?
CVE-2026-54157 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54157 actively exploited?
CVE-2026-54157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 75.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54157?
CVE-2026-54157 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-54157?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54157, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54157

Explore →

Is Your Infrastructure Affected by CVE-2026-54157?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs