ServiceNow AI Platform: Improper Access Control
CVE-2026-18886 is a critical-severity improper access control vulnerability in ServiceNow AI Platform from ServiceNow, with a CVSS 4.0 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 12 Hot Fix 3b, Yokohama Patch 13 Hot Fix 4 as the first without the flaw, so updating ServiceNow AI Platform to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 5.04% chance of exploitation within 30 days, which is in the top 7.58% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update ServiceNow AI Platform to Xanadu Patch 11 Hot Fix 7a or Yokohama Patch 12 Hot Fix 3b or Yokohama Patch 13 Hot Fix 4 or Zurich Patch 7b Hot Fix 3, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ServiceNow | ServiceNow AI Platform | before Xanadu Patch 11 Hot Fix 7a; before Yokohama Patch 12 Hot Fix 3b; before Yokohama Patch 13 Hot Fix 4; before Zurich Patch 7b Hot Fix 3; before Zurich Patch 8 Hot Fix 5; before Zurich Patch 9 Hot Fix 6; before Zurich Patch 10 Hot Fix 2m (m-branch); before Zurich Patch 10 Hot Fix 3 (standard); and 7 more ranges | Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 12 Hot Fix 3b, Yokohama Patch 13 Hot Fix 4, Zurich Patch 7b Hot Fix 3, Zurich Patch 8 Hot Fix 5, Zurich Patch 9 Hot Fix 6 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- HighSerious loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- HighSerious loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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. Scored by CNA (servicenow.com).
Official description
ServiceNow has remediated an improper access control vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to create or modify instance data beyond what was intended, resulting in privilege escalation. ServiceNow deployed a security update to hosted instances and ServiceNow provided the update to our partners and self-hosted customers. We are not currently aware of exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in ServiceNow AI Platform
- 7.1 High severity
- 9.4 Critical severity
- 9.3 Critical severity
- 8.7 High severity
- 8.7 High severity
- 8.4 High severity
Recent Improper Access Control vulnerabilities
- 8.6 High severity
- 9.8 Critical severity
- 9.9 Critical severity
- 9.0 Critical severity
- 9.1 Critical severity
- 8.2 High severity
Spotted an error? Tell us.