{"id":"CVE-2026-111388","kind":"vulnerability","aliases":["CVE-2026-111388"],"related":[],"title":"Frappe: per-user IP allowlist skipped for API key and OAuth logins","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.","summary":"Frappe Framework does not apply a user's restrict_ip allowlist to API key, OAuth and header-based logins, only to session logins. An attacker holding a valid API key, OAuth token or header credential can use it from IP addresses the allowlist was meant to block.","severity":"medium","cvss":5.4,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["erpnext","frappe","runtime","self-hosted"],"not_affected_if":["no-restrict-ip-set","session-login-only","upgraded"],"how_to_check":"- Check the Frappe version with `bench version` or the `frappe` entry in `apps.txt`/`bench version` output; affected versions are below `15.120.0` and `16.x` below `16.33.0`.\n- List users with an IP restriction set: query the User doctype for a non-empty `restrict_ip` field.\n- Review API keys and OAuth clients tied to those users for use from unexpected addresses in the access logs.","fix":"- Upgrade Frappe to `15.120.0` or `16.33.0` or later.\n- Until upgraded, rotate API keys and OAuth tokens for users with `restrict_ip` set, and block the relevant API routes at the network edge for addresses outside the allowlist.","status":"open","published_at":"2026-10-16T03:18:06+00:00","first_seen_at":"2026-10-23T21:57:12+00:00","triaged_at":"2026-10-25T04:18:41+00:00","updated_at":"2026-10-25T04:18:41+00:00","category":"runtime","confidence":0.6,"triage":{"at":"2026-10-25T04:18:41Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade Frappe to `15.120.0` or `16.33.0` or later.\n- Until upgraded, rotate API keys and OAuth tokens for users with `restrict_ip` set, and block the relevant API routes at the network edge for addresses outside the allowlist.","reach":"internet","title":"Frappe: per-user IP allowlist skipped for API key and OAuth logins","impact":"medium","summary":"Frappe Framework does not apply a user's restrict_ip allowlist to API key, OAuth and header-based logins, only to session logins. An attacker holding a valid API key, OAuth token or header credential can use it from IP addresses the allowlist was meant to block.","category":"runtime","nicknames":[],"who_cares":["frappe","erpnext","self-hosted"],"confidence":0.6,"needs_auth":"yes","worst_case":"Stolen API key or token works from IPs the allowlist should block","analyst_note":"","how_to_check":"- Check the Frappe version with `bench version` or the `frappe` entry in `apps.txt`/`bench version` output; affected versions are below `15.120.0` and `16.x` below `16.33.0`.\n- List users with an IP restriction set: query the User doctype for a non-empty `restrict_ip` field.\n- Review API keys and OAuth clients tied to those users for use from unexpected addresses in the access logs.","needs_analyst":false,"not_affected_if":["no-restrict-ip-set","session-login-only","upgraded"],"who_is_affected":"Sites that use the per-user restrict_ip setting in Frappe or ERPNext to limit where a user can log in from, and that also issue API keys, OAuth tokens or header-based credentials to those users. A site without per-user IP restrictions, or one that only uses session logins, is not exposed by this flaw. The attacker must already hold a valid credential of one of the affected types.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"medium"},"cost_usd":0.000677,"input_tokens":3351,"output_tokens":683,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-111388':16A,19A '-2026':15A,18A '15.120.0':77C '16':79C '16.33.0':82C 'access':129C 'address':67B,119C 'allowlist':6A,36B,69B,92C,122C 'api':9A,38B,55B,100C 'appli':30B 'attack':51B,108C 'authent':97C,107C,116C 'base':44B,106C,128C 'block':73B 'configur':125C 'credenti':61B,111C 'cve':14A,17A 'defeat':123C 'enforc':85C 'erpnext':20B 'framework':27B,75C 'frapp':1A,21B,26B,74C 'header':43B,60B,105C 'header-bas':42B,104C 'hold':52B,109C 'host':25B 'includ':99C 'ip':5A,35B,66B,91C,118C 'key':10A,39B,56B,101C 'login':13A,45B,49B 'meant':71B 'method':98C 'network':127C 'network-bas':126C 'non':95C 'non-sess':94C 'oauth':12A,40B,57B,102C 'outsid':120C 'per':3A,88C 'per-us':2A,87C 'restrict':34B,90C,130C 'runtim':22B 'self':24B 'self-host':23B 'session':48B,96C 'skip':7A 'token':58B 'type':114C 'use':63B 'user':4A,32B,89C 'valid':54B,110C 'x':80C","nicknames":[],"mitigations":[],"who_affected":"Sites that use the per-user restrict_ip setting in Frappe or ERPNext to limit where a user can log in from, and that also issue API keys, OAuth tokens or header-based credentials to those users. A site without per-user IP restrictions, or one that only uses session logins, is not exposed by this flaw. The attacker must already hold a valid credential of one of the affected types.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-16T03:18:06+00:00","kev":null,"cvss_vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-111388","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-111388","severity":null,"published_at":"2026-10-16T03:18:06+00:00","modified_at":"2026-10-16T17:17:33+00:00","first_seen_at":"2026-10-23T21:57:12+00:00","fetched_at":"2026-10-23T22:28:54+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}