# CVE-2026-109600: Frappe before 16.31.0 Improper Access Control in Document Follow Notifications

> Disabled users continue receiving email notifications for followed documents, leaking activity data to unauthorized accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-55m4-gj6h-q6rc, GHSA-gx67-v447-pgg3

## What is CVE-2026-109600?

CVE-2026-109600 is a medium-severity missing authorization vulnerability in frappe, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Frappe Framework before 15.118.0 and 16.x before 16.31.0 does not check whether a user account is disabled before sending Document Follow email notifications. A disabled user who previously followed documents continues to receive email updates about activity on those documents after their access should have been revoked.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109600 being exploited?

There is no known exploitation of CVE-2026-109600 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109600 is a medium-severity missing authorization vulnerability in frappe, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109600 in the wild and no public exploit code.

Affected product: frappe. 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-109600/ (Markdown: https://insights.sbomify.com/CVE-2026-109600/index.md)
```

## Sources

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

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