ServiceNow AI platform has been hit with three CVSS 10.0 vulnerabilities that allow unauthenticated remote attackers to execute arbitrary code and SQL commands, putting global enterprise ITSM deployments at immediate risk.
Many organizations run their entire IT service desk, ticket workflows, asset management, and parts of automated operations on a single ServiceNow instance. An attacker gaining control of this central system obtains not only data but also the operational console for the company’s IT processes.
Three maximum-severity flaws
On August 27, ServiceNow published an advisory covering four vulnerabilities. The three rated CVSS 10.0 are:
- CVE-2026-18885 – Code injection in the GraphQL Composite Data API that permits unauthenticated attackers to run arbitrary code and read or modify instance data.
- CVE-2026-18886 – Access-control flaw in the system configuration image upload processor allowing unauthorized users to create or alter instance data and escalate privileges.
- CVE-2026-74820 – SQL injection triggered through the ORDER BY clause of dynamic schemas, enabling unauthenticated attackers to execute arbitrary SQL against the underlying database.
A fourth issue, CVE-2026-6876 (CVSS 8.7), concerns sandbox escape on the Now platform and also permits unauthenticated code execution.
All three 10.0 flaws share the same CVSS 4.0 attack vector: network-reachable, low complexity, no privileges, and no user interaction required, with high impact on confidentiality, integrity, and availability.
Why the disclosure is especially concerning
ServiceNow serves as the core ITSM platform for numerous large enterprises. Full compromise therefore grants attackers control over ticket handling, change management, CMDB assets, and security orchestration workflows.
The disclosure follows a July report of another pre-authentication sandbox escape (CVE-2026-6875) that threat intelligence firm Defused observed being exploited in the wild. ServiceNow has now applied patches to its own hosted instances and released hotfixes for partners and self-hosted customers. Organizations running self-managed deployments must therefore handle remediation themselves.
Self-assessment of severity scores
The three 10.0 scores were assigned by ServiceNow acting as a CVE Numbering Authority. Because NIST is currently limiting enrichment to vulnerabilities listed in CISA KEV or affecting federal systems, no independent verification of the ratings has occurred yet. ServiceNow reports no observed in-the-wild exploitation or public exploit code for the newly disclosed issues.
Immediate actions for security teams
Self-hosted customers should:
- Verify whether their ServiceNow instances are reachable from the internet or low-privilege network segments and restrict access where possible.
- Apply the corresponding Hot Fix releases for the affected branches (Xanadu, Yokohama, Zurich, Australia) without delay.
- Review configuration image upload logs, database query history, and unauthorized high-privilege activity.
- Add detection rules for anomalous GraphQL and ORDER BY injection patterns to WAF or IDS platforms.
The combination of three maximum-severity vulnerabilities and the platform’s central role in enterprise IT operations makes rapid patching essential.
