Security readout for executives and security teams
Plain-English summary
Wekan versions before 10.38 can crash when an invalid authentication token reaches certain board export endpoints. A successful trigger may interrupt service for every user, but the disclosed issue does not expose or modify data. Wekan 10.38 corrects the faulty error handling.
Executive priority
Prioritize upgrading exposed or operationally critical Wekan instances promptly. The risk is service-wide availability loss rather than data theft. Schedule other affected internal instances into the next expedited maintenance window and monitor for abnormal restarts until remediation is confirmed.
Technical view
Four REST export handlers dereferenced user._id after ReactiveCache.getUser() could return undefined for an unknown authToken. The resulting TypeError in an asynchronous route could become an unhandled rejection and terminate the Wekan process. Version 10.38 adds 401 checks and safeRoute() exception handling.
Likely exposure
Exposure applies to Wekan installations below 10.38 where the affected board export endpoints are network-accessible. The supplied CVSS vector indicates low complexity and low privileges. Internet-facing or business-critical installations have greater operational risk, although actual exposure depends on deployment configuration.
Exploitation context
The source bundle does not report active exploitation, and this CVE is not listed as KEV. The described impact is remote denial of service through process termination. Evidence does not establish exploit reliability, observed attacks, or confidentiality and integrity impact.
Researcher notes
Affected routes are board export, attachment export, CSV export, and Excel export handlers. The root cause is CWE-476 null or undefined dereference compounded by asynchronous exception handling. The published fix combines explicit authentication failure responses with route-level exception containment.
Mitigation direction
- Upgrade Wekan to version 10.38 or later.
- Confirm the deployed build includes the 401 token guards and safeRoute() wrappers.
- Restrict access to affected export endpoints until upgrading, where operationally feasible.
- Monitor Wekan process restarts and unhandled rejection errors.
Validation and detection
- Inventory every Wekan deployment and record its running version.
- Confirm no production instance remains below version 10.38.
- In an authorized test environment, verify invalid export authentication receives a controlled 401 response.
- Confirm malformed export requests do not terminate or restart the Wekan process.
- Review logs for TypeError, unhandled rejection, and unexpected restart events involving export routes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-68901 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6GitHub_MVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wekan/wekan/security/advisories/GHSA-3gcg-g6rf-w2rxCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/wekan/wekan/commit/40de1799aed7c31494579659850578691171d895CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wekan/wekan/releases/tag/v10.38CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.