Quick answers
- Is CVE-2026-86120 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86120 being exploited in the wild.
- How severe is CVE-2026-86120?
- Medium severity, with a CVSS score of 4.3, published 5 September 2026.
- Which products and versions are affected?
- APITable through 1.13.0-beta.1.
- Is there a fix for CVE-2026-86120?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86120 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86120?
- Check whether you run APITable 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.
Technical details
The vulnerability is an incorrect authorization flaw in the NodePermissionGuard middleware that fails to enforce node-level access control when permission lookups throw exceptions. The guard's matchPermissions method catches all exceptions from the NodePermissionService.getNodeRole() call and silently suppresses them with an empty catch block, causing the guard to return true (allow access) regardless of whether the permission check succeeded or failed. Attackers with valid Fusion API tokens can exploit this by triggering exceptions during permission lookups to bypass access controls and write attachments to private datasheets they have been explicitly denied access to. The vulnerability is network-accessible via the Fusion API endpoint and requires only a valid API token. A patch addressing the exception handling logic is available.
Affected products
- APITable APITable through 1.13.0-beta.1
Timeline
- 2026-09-05: disclosed