Quick answers
- Is CVE-2025-59426 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-59426 being exploited in the wild.
- How severe is CVE-2025-59426?
- Low severity, with a CVSS score of 3.1, published 24 September 2025.
- Which products and versions are affected?
- LobeHub Lobe Chat < 1.130.1; @lobehub/chat (npm) SEMVER:introduced=0,fixed=1.130.1.
- Is there a fix for CVE-2025-59426?
- Yes. @lobehub/chat (npm): upgrade to 1.130.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-59426 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-59426?
- Check whether you run LobeHub Lobe Chat or @lobehub/chat (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @lobehub/chat (npm): upgrade to 1.130.1 or later
npm install @lobehub/chat@1.130.1
Technical details
The vulnerability is an open redirect (CWE-601) in the OIDC callback handler. The vulnerable code in the /oidc/consent route constructs the final redirect URL using the X-Forwarded-Host and X-Forwarded-Proto headers, trusting them without validation. An attacker can craft HTTP requests with malicious X-Forwarded-Host headers (e.g., `X-Forwarded-Host: google.com`) to trigger redirects to attacker-controlled domains. This requires user interaction (the user must click or follow the redirect) and network access to send the request. The attack is particularly effective in deployments where reverse proxies forward client-supplied headers as-is. The vulnerability is patched in version 1.130.1.
Affected products
- lobehub lobe-chat < 1.130.1
Identifiers
- CVE-2025-59426
- GHSA-xph5-278p-26qx
Timeline
- 2025-09-24: disclosed
- 2025-09-24: patched: Fixed in version 1.130.1
- 2025-09-25: other: CVE-2025-59426 published