CVE-2025-62505: @lobehub/chat Lobe Chat Vulnerable To Server-Side Vulnerability

LOW
Advisory Identifier: GHSA-fgx4-p8xf-qhp9
CVSS 3.0
CWE-918
Published
Advisory Summary

CVE-2025-62505 is a LOW (CVSS 3.0) lobe chat vulnerable to server-side vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting @lobehub/chat libraries in the npm ecosystem. The issue involves lobe chat vulnerable to server-side request forgery with native web fetch module. Remediation is available by upgrading affected packages to version 1.136.2.

CVE-2025-62505 at a Glance

CVE Identifier CVE-2025-62505
GHSA Identifier GHSA-fgx4-p8xf-qhp9
Severity LOW
CVSS v3.1 Base Score 3.0
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product @lobehub/chat
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 3.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-62505

To remediate this vulnerability, upgrade all affected @lobehub/chat dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@lobehub/chat fixed: 1.136.2
npm install @lobehub/chat@1.136.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @lobehub/chat

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-62505, inspect your project dependencies using npm:

npm ls @lobehub/chat

Analyze the terminal output to locate any version of @lobehub/chat in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.136.2), your application is affected.

Note: The npm ls @lobehub/chat command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In @lobehub/chat, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Vulnerability Description --- Vulnerability Overview - When the client sends an arbitrary URL array and impl: ["naive"] to the tRPC endpoint tools.search.crawlPages, the server issues outbound HTTP requests directly to those URLs. There is no defensive logic that restricts or validates requests to internal networks (127.0.0.1, localhost, private ranges) or metadata endpoints (169.254.169.254). - Flow: client input (urls, impls) → service invocation in the tRPC router → the service passes the URLs to Crawler.crawl → the Crawler prioritizes the user-specified impls (naive) → the naive implementation performs a server-side fetch(url) as-is (SSRF) → the server collects responses from internal resources. - In the dev environment, authentication can be bypassed using the lobe-auth-dev-backend-api: 1 header (production requires a valid token). In the PoC, this was used to successfully retrieve the internal API at localhost:8889 from the server side. Vulnerable Code https://github.com/lobehub/lobe-chat/blob/d942a635b36a231156c60d824afa573af8032572/packages/web-crawler/src/crawImpl/naive.ts#L39-L45 ### PoC --- PoC Description - In dev mode, we made a single tRPC call using the auth-bypass header lobe-auth-dev-backend-api: 1. Since tRPC requires the body to be in the form {"json": { ... }}, we placed urls and impls: ["naive"] inside json to induce the server to request the internal URL (http://localhost:8889/internel-api). - The response follows tRPC’s wrapping structure, so the actual body of the internal API is included as a string (JSON string) at result.data.json.results[0].data.content. We post-process it with jq for readability. curl Example ```bash curl -sS -X POST 'http://localhost:3010/trpc/tools/search.crawlPages' \ -H 'Content-Type: application/json' \ -H 'lobe-auth-dev-backend-api: 1' \ --data '{"json":{"urls":["http://localhost:8889/internal-api"],"impls":["naive"]}}' | jq -r '.result.data.json.results[0].data.content' | jq . ``` <img width="1916" height="851" alt="poc" src="https://github.com/user-attachments/assets/f3ad34da-f8ac-4e29-9360-3cf1d1f706d8" /> ### Impact --- - Since the server performs outbound requests to internal networks, localhost, and metadata endpoints, an attacker can abuse the server’s network position to access internal resources (internal APIs, management ports, cloud metadata, etc.). - As a result, this can lead to exposure of internal system information, leakage of authentication tokens/secret keys (e.g., IMDSv1/v2), misuse of internal admin interfaces, and provide a foothold for further lateral movement. - By leveraging user-supplied impls to force the unfiltered naive implementation, SSRF defenses—such as blocking private/metadata IPs, DNS re-validation/re-resolution, and redirect restrictions—can be bypassed.

CVE-2025-62505 Affected @lobehub/chat Versions

1 component(s)
Fixed Versions:
1.136.2
Product / Package Ecosystem Affected Versions Fixed Version
@lobehub/chat
npm
< 1.136.2
1.136.2

References

Frequently Asked Questions

What is CVE-2025-62505?
CVE-2025-62505 is a security vulnerability in @lobehub/chat involving Lobe Chat vulnerable to Server-Side Request Forgery with native web fetch module under CWE-918: Server-Side Request Forgery (SSRF).
Which @lobehub/chat versions are affected?
Affected versions include releases prior to 1.136.2 across affected packages: @lobehub/chat.
What version fixes CVE-2025-62505?
Upgrading to 1.136.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @lobehub/chat affected?
Yes, @lobehub/chat is affected in releases prior to 1.136.2. Upgrade your dependency to 1.136.2 or later.
What is the CVSS score of CVE-2025-62505?
CVE-2025-62505 has a CVSS v3.1 base score of 3.0 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2025-62505?
CVE-2025-62505 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2025-62505?
Run the dependency tree command: 'npm ls @lobehub/chat'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fgx4-p8xf-qhp9",
  "modified" : "2025-10-17T21:32:47Z",
  "published" : "2025-10-17T17:46:09Z",
  "aliases" : [ "CVE-2025-62505" ],
  "summary" : "Lobe Chat vulnerable to Server-Side Request Forgery with native web fetch module",
  "details" : "### Vulnerability Description\n---\n\nVulnerability Overview\n \n- When the client sends an arbitrary URL array and impl: [\"naive\"] to the tRPC endpoint tools.search.crawlPages, the server issues outbound HTTP requests directly to those URLs. There is no defensive logic that restricts or validates requests to internal networks (127.0.0.1, localhost, private ranges) or metadata endpoints (169.254.169.254).\n\n- Flow: client input (urls, impls) → service invocation in the tRPC router → the service passes the URLs to Crawler.crawl → the Crawler prioritizes the user-specified impls (naive) → the naive implementation performs a server-side fetch(url) as-is (SSRF) → the server collects responses from internal resources.\n\n- In the dev environment, authentication can be bypassed using the lobe-auth-dev-backend-api: 1 header (production requires a valid token). In the PoC, this was used to successfully retrieve the internal API at localhost:8889 from the server side.\n\nVulnerable Code\n \n\nhttps://github.com/lobehub/lobe-chat/blob/d942a635b36a231156c60d824afa573af8032572/packages/web-crawler/src/crawImpl/naive.ts#L39-L45\n\n\n### PoC\n---\n\nPoC Description\n\n- In dev mode, we made a single tRPC call using the auth-bypass header lobe-auth-dev-backend-api: 1. Since tRPC requires the body to be in the form {\"json\": { ... }}, we placed urls and impls: [\"naive\"] inside json to induce the server to request the internal URL (http://localhost:8889/internel-api).\n\n- The response follows tRPC’s wrapping structure, so the actual body of the internal API is included as a string (JSON string) at result.data.json.results[0].data.content. We post-process it with jq for readability.\n\ncurl Example \n\n```bash\ncurl -sS -X POST 'http://localhost:3010/trpc/tools/search.crawlPages' \\\n  -H 'Content-Type: application/json' \\\n  -H 'lobe-auth-dev-backend-api: 1' \\\n  --data '{\"json\":{\"urls\":[\"http://localhost:8889/internal-api\"],\"impls\":[\"naive\"]}}' | jq -r '.result.data.json.results[0].data.content' | jq .\n```\n<img width=\"1916\" height=\"851\" alt=\"poc\" src=\"https://github.com/user-attachments/assets/f3ad34da-f8ac-4e29-9360-3cf1d1f706d8\" />\n\n\n### Impact\n---\n\n- Since the server performs outbound requests to internal networks, localhost, and metadata endpoints, an attacker can abuse the server’s network position to access internal resources (internal APIs, management ports, cloud metadata, etc.).\n\n- As a result, this can lead to exposure of internal system information, leakage of authentication tokens/secret keys (e.g., IMDSv1/v2), misuse of internal admin interfaces, and provide a foothold for further lateral movement.\n\n- By leveraging user-supplied impls to force the unfiltered naive implementation, SSRF defenses—such as blocking private/metadata IPs, DNS re-validation/re-resolution, and redirect restrictions—can be bypassed.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@lobehub/chat"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.136.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.136.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lobehub/lobe-chat/security/advisories/GHSA-fgx4-p8xf-qhp9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62505"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lobehub/lobe-chat/commit/8d59583dca16f218b99213d641733d8ba77f182c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lobehub/lobe-chat"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lobehub/lobe-chat/blob/d942a635b36a231156c60d824afa573af8032572/packages/web-crawler/src/crawImpl/naive.ts#L39-L45"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-17T17:46:09Z",
    "nvd_published_at" : "2025-10-17T19:15:38Z"
  }
}