CVE-2026-23835

MEDIUMNVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-5006 (ENISA EUVD) · GHSA-wrrr-8jcv-wjf5 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

LobeHub is an open source human-and-AI-agent network. Prior to version 1.143.3, the file upload feature in Knowledge Base > File Upload does not validate the integrity of the upload request, allowing users to intercept and modify the request parameters. As a result, it is possible to create arbitrary files in abnormal or unintended paths. In addition, since lobechat.com relies on the size parameter from the request to calculate file usage, an attacker can manipulate this value to misrepresent the actual file size, such as uploading a 1 GB file while reporting it as 10 MB, or falsely declaring a 10 MB file as a 1 GB file. By manipulating the size value provided in the client upload request, it is possible to bypass the monthly upload quota enforced by the server and continuously upload files beyond the intended storage and traffic limits. This abuse can result in a discrepancy between actual resource consumption and billing calculations, causing direct financial impact to the service operator. Additionally, exhaustion of storage or related resources may lead to degraded service availability, including failed uploads, delayed content delivery, or temporary suspension of upload functionality for legitimate users. A single malicious user can also negatively affect other users or projects sharing the same subscription plan, effectively causing an indirect denial of service (DoS). Furthermore, excessive and unaccounted-for uploads can distort monitoring metrics and overload downstream systems such as backup processes, malware scanning, and media processing pipelines, ultimately undermining overall operational stability and service reliability. Version 1.143.3 contains a patch for the issue.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): 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
0.4%
EPSS %ILE
30th
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 (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

January 30, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Improper Authorization in Presigned Upload: User-controlled object key enables cross-namespace upload attempts and quota bypass · Advisory · lobehub/lobehub · GitHub

https://github.com/lobehub/lobehub/security/advisories/GHSA-wrrr-8jcv-wjf5

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@lobehub/chat @ 1.143.3 (fixes < 1.143.3)—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 1.143.3: fixed in 1.143.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 99 of 231 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-23835?
CVE-2026-23835 is a medium-severity vulnerability; its CVE record was published on January 30, 2026. LobeHub is an open source human-and-AI-agent network. Prior to version 1.143.3, the file upload feature in Knowledge Base > File Upload does not validate the integrity of the upload request, allowing users to intercept and modify the request parameters. As a result, it is possible to create…
When was the CVE record for CVE-2026-23835 published?
The CVE record for CVE-2026-23835 was published on January 30, 2026. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-23835 actively exploited?
CVE-2026-23835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23835?
CVE-2026-23835 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-23835?
A fix for CVE-2026-23835 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-2026-23835

Explore →

Is Your Infrastructure Affected by CVE-2026-23835?

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

Book a Demo →Browse All CVEs