CVE-2026-101004
Received Received - Intake

Missing Authentication in NotionNext via API Cache

Publication date: 2026-09-28

Last updated on: 2026-09-28

Assigner: VulDB

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-28
Last Modified
2026-09-28
Generated
2026-09-28
AI Q&A
2026-09-28
EPSS Evaluated
N/A
NVD
CVE-2026-101004
EUVD
EUVD-2026-88090

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
notionnext-org notionnext 4.10.10
notionnext-org notionnext to 4.10.10 (inc)
notionnext-org notionnext From 4.1.0 (inc) to 4.9.5.3 (exc)
notionnext-org notionnext From 4.9.5.7 (inc) to 4.10.10 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in NotionNext up to version 4.10.10, specifically in the cleanCache function of pages/api/cache.js. It allows remote attackers to bypass authentication by manipulating the token argument. Versions 4.1.0 to 4.9.5.2 are vulnerable due to missing method checks, while versions 4.9.5.7 to 4.10.10 have a guard that only works if CACHE_REVALIDATION_TOKEN is set, leaving default deployments unprotected.

Detection Guidance

Check if the NotionNext application is running versions 4.1.0 to 4.10.10. Inspect the pages/api/cache.js file for the cleanCache function. Verify if CACHE_REVALIDATION_TOKEN is configured. Test unauthenticated access to endpoints that should require authentication.

Impact Analysis

An attacker could exploit this to access sensitive data or perform unauthorized actions in the application. Since authentication is bypassed, they might manipulate cached content, steal information, or disrupt services without valid credentials.

Compliance Impact

This vulnerability allows unauthenticated remote access due to missing authentication checks in the cleanCache function. This could lead to unauthorized data access or modification, violating GDPR's data protection principles and HIPAA's access control requirements for sensitive health information.

Mitigation Strategies

Upgrade NotionNext to a version beyond 4.10.10 if available. Ensure CACHE_REVALIDATION_TOKEN is set to enforce authentication guard. Implement additional access controls or network-level protections to restrict unauthenticated requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-101004. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart