Answer in brief
CVE-2026-101004 records a Medium severity (CVSS 6.9) vulnerability in notionnext-org NotionNext Authentication Guard cache.js cleanCache missing authentication. The current sources do not mark it as known exploited. The current feed maps notionnext-org/NotionNext (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps notionnext-org/NotionNext (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| notionnext-org/NotionNextgeneric | 4.10.0 || 4.10.1 || 4.10.2 || 4.10.3 || 4.10.4 || 4.10.5 || 4.10.6 || 4.10.7 || 4.10.8 || 4.10.9 || 4.10.10 | Not reported |
Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 28, 2026
A security vulnerability has been detected in notionnext-org NotionNext up to 4.10.10. Affected by this issue is the function cleanCache of the file pages/api/cache.js of the component Authentication Guard. The manipulation of the argument token leads to missing authentication. The attack may be initiated remotely. Versions 4.1.0 - 4.9.5.2 allow unauthenticated exploitation due to missing method check. In versions 4.9.5.7 - 4.10.10 a guard present but only enforced when CACHE_REVALIDATION_TOKEN is set. Default deployments remain unprotected. The vendor was contacted early about this disclosure but did not respond in any way.
Quoted source text, attributed separately from HOL analysis.