Summary
CVE-2026-86858 is an improper access control vulnerability (CWE-284) in the ServiceNow AI Platform that allows an unauthenticated attacker to create, modify, or delete instance data beyond what was intended, in certain circumstances. The flaw carries a CVSS v4.0 base score of 8.7 (High), reflecting network exploitability with no authentication or user interaction required. ServiceNow deployed fixes to hosted instances in August 2026 and states it is not aware of any malicious exploitation in the wild.
Technical details
- Root cause: Improper access control (CWE-284) within the ServiceNow AI Platform, permitting operations that should be restricted to authenticated/authorized users.
- Trigger conditions: Occurs "in certain circumstances" on affected instances; no authentication or privileged access is required to trigger the flaw.
- Attack vector: Network — an unauthenticated actor can interact with the exposed instance remotely.
- Impact: Unauthorized creation, modification, or deletion of instance data beyond the intended scope, resulting in a high integrity impact. No confidentiality or availability impact is indicated by 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, Patch 10 Hot Fix 4a W32, and Patch 11 Hot Fix 3
- ServiceNow AI Platform, Australia release: versions prior to Patch 2 Hot Fix 4b W32, Patch 4 Hot Fix 3, and 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:N/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade to the patched release for your branch — 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.
- If no patch can be applied immediately: ServiceNow states it has already deployed the security update to hosted (cloud) instances; self-hosted and partner-hosted customers should apply the corresponding update or hotfix as soon as possible. No alternative workaround has been published, so timely patching is the recommended path to remediation.

