CVE-2026-68929

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-67310 (ENISA EUVD)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 9.3Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

FastGPT is an open-source LLM platform for building AI applications on a knowledge base. In versions prior to 4.15.2, the WeChat (iLink) share-channel endpoints authorize requests using only the public shareId, with no authenticated identity or team-ownership check. As a result, an unauthenticated attacker who knows a victim team's shareId can take that team's WeChat bot offline or hijack the channel to their own bot: the logout endpoint is gated only by an existence check yet wipes the outLink's stored WeChat token, and the QR-code status endpoint performs no authorization at all and writes attacker-supplied bot credentials into the outLink identified by shareId. By generating a QR for a victim shareId, scanning it with their own WeChat, and calling the status endpoint, an attacker binds the victim team's app to the attacker's bot, exposing the app's private responses, displacing the legitimate binding, and consuming the victim's resources. The shareId is exposed in every shared chat URL, iframe, and embed, so it is not a secret. This issue is fixed in version 4.15.2.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
38th
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

August 27, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Oct 3, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Missing authorization on WeChat (iLink) outLink endpoints: unauthenticated cross-tenant bot-token wipe (DoS) and channel hijack keyed only by the public shareId · Advisory · labring/FastGPT · GitHub

https://github.com/labring/FastGPT/security/advisories/GHSA-q4pr-3qpg-9q5v
GitHub commit

commit 81d391995b1f (labring/FastGPT)

Fix landed in labring/FastGPT commit 81d391995b1f — awaiting tagged release

https://github.com/labring/FastGPT/commit/81d391995b1f9989455267448872ff88bb1f42c9

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 152 rows 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. None are among the latest 100 rows. The 52 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-68929?
CVE-2026-68929 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. FastGPT is an open-source LLM platform for building AI applications on a knowledge base. In versions prior to 4.15.2, the WeChat (iLink) share-channel endpoints authorize requests using only the public shareId, with no authenticated identity or team-ownership check. As a result, an unauthenticated…
When was the CVE record for CVE-2026-68929 published?
The CVE record for CVE-2026-68929 was published on August 27, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-68929 actively exploited?
CVE-2026-68929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68929?
CVE-2026-68929 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68929?
The CVE record for CVE-2026-68929 names the fix: "This issue is fixed in version 4.15.2."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68929

Explore →

Is Your Infrastructure Affected by CVE-2026-68929?

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