CVE-2026-18885 — Unauthenticated Remote Code Execution in GraphQL Composite Data API
ServiceNow has remediated a code injection vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute arbitrary code in the ServiceNow platform and gain access to, or modify, instance data beyond what was intended. 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 malicious exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 7.2% (30-day exploitation probability)+14
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (ServiceNow ServiceNow AI Platform).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 94% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| ServiceNow | ServiceNow AI Platform |
< 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< Zurich Patch 10 Hot Fix 2m (m-branch)< Zurich Patch 10 Hot Fix 3 (standard) and 7 more< Zurich Patch 11< Zurich Patch 12< Australia Patch 2 Hot Fix 3< Australia Patch 3 Hot Fix 2< Australia Patch 3m< Australia Patch 4< Australia Patch 5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 4.0 | Critical | — | — | psirt@servicenow.com via NIST National Vulnerability Database |
| 10.0 | CVSS 4.0 | Critical | — | — | SN via CVE Program (cve.org) e CISA ADP |
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 (score shown at the top: psirt@servicenow.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · servicenow/servicenow ai platform
- SSVC assessment updated
- Record published
- CVSS changed · 10.0
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-86857 Authorization Bypass in ServiceNow AI Platform 21d
- High CVE-2026-86858 Unauthenticated Privilege Escalation via GraphQL in ServiceNow AI Platform 21d
- High CVE-2026-86859 Unauthenticated Arbitrary Record Disclosure in ServiceNow AI Platform 21d
- Critical CVE-2026-86860 Unauthenticated Sensitive Data Disclosure in ServiceNow AI Platform 21d
- Critical CVE-2026-13016 Unauthenticated SQL Injection in ServiceNow AI Platform 21d
- Critical CVE-2026-74820 Unauthenticated SQL Injection via Dynamic Schema ORDER BY Clause Aug 27, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-18885 is "Unauthenticated Remote Code Execution in GraphQL Composite Data API", rated Critical. It affects ServiceNow AI Platform (ServiceNow); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 10.0 describes technical severity. EPSS 7.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.