Summary
CVE-2026-86859 is an authorization bypass vulnerability in the ServiceNow AI Platform that allows an unauthenticated attacker to access data they are not entitled to view. ServiceNow has rated the issue HIGH severity (CVSS 8.7) and has released hotfixes for the affected release families. ServiceNow states it is not currently aware of malicious exploitation in the wild.
Technical details
- Root cause: An improper authorization check within the ServiceNow AI Platform allows access-control restrictions on records to be bypassed.
- Trigger conditions: No authentication or user interaction is required; an attacker only needs network access to an exposed instance.
- Attack vector: Network — the flaw is remotely exploitable over the network (AV:N, AC:L, AT:N, PR:N, UI:N per the CVSS v4.0 vector).
- Impact: Successful exploitation discloses data within the platform that the unauthenticated user would otherwise not be entitled to access, which ServiceNow notes could enable further unintended access. The vulnerability affects confidentiality only; integrity and availability are not impacted per the CVSS vector.
Affected software
- ServiceNow AI Platform, Yokohama release: versions prior to Patch 13 Hot Fix 5a
- ServiceNow AI Platform, Zurich release: versions prior to Patch 10 Hot Fix 3b, prior to Patch 10 Hot Fix 4a W32, and prior to Patch 11 Hot Fix 3
- ServiceNow AI Platform, Australia release: versions prior to Patch 2 Hot Fix 4b W32, prior to Patch 4 Hot Fix 3, and prior to Patch 5
Severity
CVSS v4.0 Base Score: 8.7 (High)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade to the fixed hotfix for your release family:
- Yokohama: Patch 13 Hot Fix 5a or later
- Zurich: Patch 10 Hot Fix 3b, Patch 10 Hot Fix 4a W32, or Patch 11 Hot Fix 3 (or later)
- Australia: Patch 2 Hot Fix 4b W32, Patch 4 Hot Fix 3, or Patch 5 (or later)
- ServiceNow has already applied the update to hosted instances; self-hosted customers and partners must apply the provided update themselves.
- If patching cannot be completed immediately: No workaround has been published by the vendor; ServiceNow recommends applying the appropriate update as soon as possible. Restrict and monitor external network access to ServiceNow instances until patched.

