# CVE-2026-101004: notionnext-org NotionNext Authentication Guard cache.js cleanCache missing authentication

> Attackers can remotely invoke the cleanCache function without authentication in default deployments, bypassing security controls in NotionNext.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-r4gw-rxqg-rfvq

## What is CVE-2026-101004?

CVE-2026-101004 is a medium-severity missing authorization vulnerability in notionnext-org NotionNext, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-101004?


## How do I fix CVE-2026-101004?

No fix has been published for CVE-2026-101004 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101004 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101004 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101004 and fix it if it is affected.

What it is: CVE-2026-101004 is a medium-severity missing authorization vulnerability in notionnext-org NotionNext, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101004 exists.

Affected product: notionnext-org NotionNext. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101004/ (Markdown: https://insights.sbomify.com/CVE-2026-101004/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101004
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101004
- OSV: https://osv.dev/vulnerability/CVE-2026-101004

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101004/
Summaries are generated and may contain mistakes; the official description above is the record.