Quick answers
- Is CVE-2026-66057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66057 being exploited in the wild.
- How severe is CVE-2026-66057?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Frappe before 15.116.0, before 16.29.0.
- Is there a fix for CVE-2026-66057?
- Yes: fixed in 15.116.0, 16.29.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66057 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-66057?
- Check whether you run Frappe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 15.116.0, 16.29.0
Technical details
The vulnerability is an open redirect in the OAuth login flow where an unsanitized client-controlled state parameter is used to select the post-authentication redirect location. An attacker can craft a state value to redirect users to arbitrary URLs. The fix replaces the JSON-encoded state with a server-side random token that resolves the redirect_to via cache lookup instead of decoding from state.
Affected products
- Frappe Frappe before 15.116.0, before 16.29.0
Timeline
- 2026-10-13: disclosed