# CVE-2026-111388: Frappe before 16.33.0 restrict_ip Allowlist Bypass via API Key, OAuth Authentication

> Attackers with valid API or OAuth credentials can bypass IP allowlist restrictions in Frappe Framework, accessing the system from unauthorized networks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-87cm-fpc4-v76f, GHSA-h9jq-7pgf-hw8q

## What is CVE-2026-111388?

CVE-2026-111388 is a medium-severity authentication bypass vulnerability in frappe, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe Framework before 15.120.0 and 16.x before 16.33.0 does not enforce the per-user restrict_ip allowlist for non-session authentication methods, including API key, OAuth, and header-based authentication. Attackers holding valid credentials of these types can authenticate from IP addresses outside the allowlist, defeating the configured network-based access restrictions.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-111388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111388 is a medium-severity authentication bypass vulnerability in frappe, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111388 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-111388/ (Markdown: https://insights.sbomify.com/CVE-2026-111388/index.md)
```

## Sources

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

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