Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-86860 Overview
ServiceNow has remediated a missing authorization vulnerability [CWE-862] in the ServiceNow AI Platform. The flaw allows an unauthenticated attacker to extract instance data beyond intended boundaries under specific conditions. Successful exploitation results in privilege escalation and exposure of sensitive instance information.
ServiceNow has already deployed security updates to hosted instances and distributed patches to partners and self-hosted customers. The vendor states it is not aware of malicious exploitation in the wild. Customers running self-hosted deployments should apply the vendor-supplied update immediately.
Critical Impact
An unauthenticated remote attacker can extract instance data and escalate privileges on affected ServiceNow AI Platform deployments without user interaction.
Affected Products
- ServiceNow AI Platform (hosted instances)
- ServiceNow AI Platform (self-hosted deployments)
- ServiceNow partner-managed instances
Discovery Timeline
- 2026-09-24 - CVE-2026-86860 published to the National Vulnerability Database (NVD)
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-86860
Vulnerability Analysis
The vulnerability is a missing authorization flaw [CWE-862] in the ServiceNow AI Platform. The platform fails to enforce authorization checks on specific requests that access instance data. An unauthenticated attacker reaching the platform over the network can issue crafted requests to retrieve data outside their intended authorization scope.
Because the request path does not validate the caller's identity or permissions, the server returns protected information to any requester meeting the exploitation preconditions. The result is unauthorized data extraction and a path to privilege escalation within the instance.
Root Cause
The root cause is an absent authorization decision point in the request-handling logic of the ServiceNow AI Platform. The affected code paths rely on implicit trust rather than enforcing explicit access control. ServiceNow has not published full technical internals of the flaw.
Attack Vector
The attack vector is network-based with low complexity. No authentication, user interaction, or elevated privileges are required to initiate the request. The attacker sends HTTP requests to an exposed ServiceNow instance endpoint and parses the returned data to harvest records or escalate privileges within the target instance scope.
The vulnerability manifests in request handlers that process instance data without a corresponding authorization decision. Refer to the ServiceNow Knowledge Base Article for vendor-specific technical details and version information.
Detection Methods for CVE-2026-86860
Indicators of Compromise
- Unauthenticated HTTP requests to ServiceNow AI Platform endpoints returning sensitive instance data in the response body.
- Unusual outbound data volumes from ServiceNow instances to unknown external IP addresses.
- Account privilege changes or new role assignments that do not correlate with legitimate administrative activity.
Detection Strategies
- Review ServiceNow access logs for requests to protected endpoints that lack a valid session or token.
- Correlate anomalous data retrieval patterns with the IP addresses and user agents issuing those requests.
- Monitor for repeated enumeration requests against instance APIs from the same source over short time windows.
Monitoring Recommendations
- Enable verbose request logging on ServiceNow instances and forward logs to a centralized SIEM for retention and analysis.
- Alert on any 200-level responses to unauthenticated API calls targeting data-bearing endpoints.
- Track privilege-assignment events and compare them against change management records.
How to Mitigate CVE-2026-86860
Immediate Actions Required
- Apply the ServiceNow security update to all self-hosted instances without delay.
- Confirm hosted instances have received the vendor-deployed patch by consulting the ServiceNow support portal.
- Audit instance access logs for the period preceding the patch to identify potential prior exploitation.
- Rotate credentials and API tokens for accounts whose data may have been exposed.
Patch Information
ServiceNow has deployed the fix to hosted instances and provided updates to partners and self-hosted customers. Patch details, affected versions, and upgrade paths are documented in the ServiceNow Knowledge Base Article KB3159623.
Workarounds
- Restrict network access to ServiceNow AI Platform endpoints using IP allowlisting or a web application firewall until patches are applied.
- Place the instance behind an authenticating reverse proxy that rejects unauthenticated requests to sensitive paths.
- Disable or limit exposure of AI Platform features that are not actively used in production.
# Example: restrict access to ServiceNow instance using firewall allowlist
# Replace with your organization's trusted CIDR ranges
iptables -A INPUT -p tcp --dport 443 -s 203.0.113.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
