CVE-2024-32964

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-05-10. NVD baseline CVSS 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2024-1699 (ENISA EUVD) · GHSA-mxhq-xw3g-rphc (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 53%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 53%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Lobe Chat is a chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Prior to 0.150.6, lobe-chat had an unauthorized Server-Side Request Forgery vulnerability in the /api/proxy endpoint. An attacker can construct malicious requests to cause Server-Side Request Forgery without logging in, attack intranet services, and leak sensitive information.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
67
EG Risk 67/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
53%
EPSS %ILE
98th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
53% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 14, 2024

Last Modified

September 30, 2025

Advisory Details (2)

Auto-updated Jul 23, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

【Critical】`/api/proxy` endpoint ssrf vulnerability in lobe-chat · Advisory · lobehub/lobehub · GitHub

https://github.com/lobehub/lobe-chat/security/advisories/GHSA-mxhq-xw3g-rphc
GitHub commit

commit 465665a73555 (lobehub/lobe-chat)

Fix landed in lobehub/lobe-chat commit 465665a73555 — awaiting tagged release

https://github.com/lobehub/lobe-chat/commit/465665a735556669ee30446c7ea9049a20cc7c37

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@lobehub/chat @ 0.150.6 (fixes <= 0.150.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@lobehub/chat—
  • every version up to 0.150.6: fixed in 0.150.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 187 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 13:44 UTCEG score recompute
  2. 2026-11-02 13:44 UTCGHSA enrichmentGHSA-mxhq-xw3g-rphc · GitHub severity CRITICAL · GitHub CVSS 9.0
  3. 2026-11-01 15:54 UTCGHSA enrichmentGHSA-mxhq-xw3g-rphc · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-mxhq-xw3g-rphc · GitHub severity CRITICAL · GitHub CVSS 9.0
  5. 2026-11-01 08:14 UTCEG score recompute
  6. 2026-10-31 18:04 UTCEG score recompute
  7. 2026-10-31 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  8. 2026-10-30 20:14 UTCEG score recompute
  9. 2026-10-30 16:32 UTCEPSS rescoreEPSS 53% · 98th percentile
  10. 2026-10-29 22:24 UTCEG score recompute
  11. 2026-10-29 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  12. 2026-10-29 00:36 UTCEG score recompute
  13. 2026-10-28 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  14. 2026-10-28 02:43 UTCEG score recompute
  15. 2026-10-27 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  16. 2026-10-27 04:48 UTCEG score recompute
  17. 2026-10-26 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  18. 2026-10-25 17:11 UTCEG score recompute
  19. 2026-10-25 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  20. 2026-10-25 04:48 UTCEG score recompute
  21. 2026-10-24 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  22. 2026-10-24 06:59 UTCEG score recompute
  23. 2026-10-23 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  24. 2026-10-23 09:09 UTCEG score recompute
  25. 2026-10-22 11:18 UTCEG score recompute
Show 69 more
  1. 2026-10-21 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  2. 2026-10-21 13:29 UTCEG score recompute
  3. 2026-10-20 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  4. 2026-10-20 15:16 UTCEG score recompute
  5. 2026-10-19 16:29 UTCEPSS rescoreEPSS 53% · 98th percentile
  6. 2026-10-18 17:52 UTCEG score recompute
  7. 2026-10-18 07:16 UTCEG score recompute
  8. 2026-10-17 20:02 UTCEG score recompute
  9. 2026-10-17 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  10. 2026-10-16 22:10 UTCEG score recompute
  11. 2026-10-16 16:36 UTCEPSS rescoreEPSS 53% · 98th percentile
  12. 2026-10-15 18:45 UTCEG score recompute
  13. 2026-10-15 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  14. 2026-10-14 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  15. 2026-10-14 12:24 UTCEG score recompute
  16. 2026-10-13 16:30 UTCEPSS rescoreEPSS 53% · 98th percentile
  17. 2026-10-12 17:55 UTCEG score recompute
  18. 2026-10-12 16:31 UTCEPSS rescoreEPSS 53% · 98th percentile
  19. 2026-10-12 14:20 UTCEG score recompute
  20. 2026-10-11 21:19 UTCEG score recompute
  21. 2026-10-11 16:12 UTCEG score recompute
  22. 2026-10-11 13:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  23. 2026-10-11 03:31 UTCOSV refresh
  24. 2026-10-10 19:58 UTCEPSS rescoreEPSS 53% · 98th percentile
  25. 2026-10-09 20:05 UTCEPSS rescoreEPSS 53% · 98th percentile
  26. 2026-10-08 17:07 UTCEPSS rescoreEPSS 53% · 98th percentile
  27. 2026-10-07 23:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  28. 2026-10-06 15:15 UTCEPSS rescoreEPSS 53% · 98th percentile
  29. 2026-10-03 14:24 UTCEPSS rescoreEPSS 53% · 98th percentile
  30. 2026-10-01 19:48 UTCEPSS rescoreEPSS 53% · 98th percentile
  31. 2026-09-30 19:44 UTCEG score recompute
  32. 2026-09-30 15:01 UTCEPSS rescoreEPSS 53% · 98th percentile
  33. 2026-09-27 13:43 UTCEPSS rescoreEPSS 53% · 98th percentile
  34. 2026-09-26 15:57 UTCEPSS rescoreEPSS 53% · 98th percentile
  35. 2026-09-24 14:01 UTCEPSS rescoreEPSS 53% · 98th percentile
  36. 2026-09-23 13:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  37. 2026-09-22 14:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  38. 2026-09-21 14:49 UTCOSV refresh
  39. 2026-09-20 20:14 UTCEPSS rescoreEPSS 53% · 98th percentile
  40. 2026-09-19 15:40 UTCEPSS rescoreEPSS 53% · 98th percentile
  41. 2026-09-18 19:26 UTCEPSS rescoreEPSS 53% · 98th percentile
  42. 2026-09-16 14:06 UTCEPSS rescoreEPSS 53% · 98th percentile
  43. 2026-09-15 03:08 UTCEPSS rescoreEPSS 53% · 98th percentile
  44. 2026-09-12 14:59 UTCEPSS rescoreEPSS 53% · 98th percentile
  45. 2026-09-11 14:51 UTCEPSS rescoreEPSS 53% · 98th percentile
  46. 2026-09-11 09:35 UTCEPSS rescoreEPSS 53% · 98th percentile
  47. 2026-09-08 21:58 UTCEPSS rescoreEPSS 53% · 98th percentile
  48. 2026-09-06 13:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  49. 2026-09-05 15:26 UTCEPSS rescoreEPSS 53% · 98th percentile
  50. 2026-09-04 13:58 UTCEPSS rescoreEPSS 53% · 98th percentile
  51. 2026-09-02 14:10 UTCEPSS rescoreEPSS 53% · 98th percentile
  52. 2026-09-02 12:14 UTCOSV refresh
  53. 2026-09-01 13:52 UTCEPSS rescoreEPSS 53% · 98th percentile
  54. 2026-08-30 19:15 UTCEPSS rescoreEPSS 53% · 98th percentile
  55. 2026-08-30 01:20 UTCEPSS rescoreEPSS 53% · 98th percentile
  56. 2026-08-28 21:39 UTCEPSS rescoreEPSS 53% · 98th percentile
  57. 2026-08-27 14:23 UTCEPSS rescoreEPSS 53% · 98th percentile
  58. 2026-08-26 14:44 UTCEPSS rescoreEPSS 53% · 98th percentile
  59. 2026-08-25 13:47 UTCEPSS rescoreEPSS 53% · 98th percentile
  60. 2026-08-24 14:15 UTCEPSS rescoreEPSS 53% · 98th percentile
  61. 2026-08-23 00:17 UTCEPSS rescoreEPSS 53% · 98th percentile
  62. 2026-08-21 23:47 UTCEPSS rescoreEPSS 53% · 98th percentile
  63. 2026-08-20 22:53 UTCEPSS rescoreEPSS 53% · 98th percentile
  64. 2026-08-19 17:02 UTCEPSS rescoreEPSS 53% · 98th percentile
  65. 2026-08-18 13:46 UTCEPSS rescoreEPSS 53% · 98th percentile
  66. 2026-08-17 13:45 UTCEPSS rescoreEPSS 53% · 98th percentile
  67. 2026-08-16 14:54 UTCEPSS rescoreEPSS 53% · 98th percentile
  68. 2026-08-16 09:38 UTCOSV refresh
  69. 2026-08-16 02:13 UTCEPSS rescoreEPSS 53% · 98th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2024/CVE-2024-32964.yaml
    Published Oct 5, 2024

    Lobe Chat <= v0.150.5 - Server-Side Request Forgery

    Open source ↗

Frequently asked(5)

What is CVE-2024-32964?
CVE-2024-32964 is a critical-severity vulnerability; its CVE record was published on May 14, 2024. Lobe Chat is a chatbot framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Prior to 0.150.6, lobe-chat had an unauthorized Server-Side Request Forgery vulnerability in the /api/proxy endpoint. An attacker can construct malicious requests to cause…
When was the CVE record for CVE-2024-32964 published?
The CVE record for CVE-2024-32964 was published on May 14, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2025; the record at its source may have been updated since.
Is CVE-2024-32964 actively exploited?
CVE-2024-32964 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 53% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32964?
CVE-2024-32964 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2024-32964?
A fix for CVE-2024-32964 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32964

Explore →

Is Your Infrastructure Affected by CVE-2024-32964?

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