CTIPilot

ServiceNow AI Platform

product · product:servicenow-ai-platform single-source

Coverage timeline
2
first 2026-07-13 → last 2026-08-29
Peak priority
high
2 high
Sources cited
8
7 hosts
Sections touched
1
trending-vulnerabilities
Co-occurring entities
6
see Co-occurring entities below
ATT&CK techniques
2
pinned v19.2 · see below

ATT&CK techniques

2 techniques observed across 2 entries, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Initial Access TA0001

T1190Exploit Public-Facing Application×2

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-08-29/servicenow-ai-platform-four-unauth-cvss10-flaws · 2026-07-13/servicenow-ai-platform-sandbox-escape-cve-2026-6875 · ATT&CK page ↗

Privilege Escalation TA0004

T1611Escape to Host×1

Adversaries may break out of a container or virtualized environment to gain access to the underlying host. This can allow an adversary access to other containerized or virtualized resources from the host level or to the host itself. In principle, containerized / virtualized resources should provide a clear separation of application functionality and be isolated from the host environment.

Evidence: 2026-07-13/servicenow-ai-platform-sandbox-escape-cve-2026-6875 · ATT&CK page ↗

Story timeline

  1. 2026-08-29CVE-2026-18885 / CVE-2026-18886 / CVE-2026-74820 / CVE-2026-6876, ServiceNow AI Platform: three unauthenticated CVSS 10.0 flaws plus a related Now Platform sandbox escape
    trending-vulnerabilitiesServiceNow patches four unauthenticated flaws in its AI Platform and Now Platform, three of them maximum severity
  2. 2026-07-13CVE-2026-6875, ServiceNow AI Platform sandbox escape lets an unauthenticated request execute code on the platform (CVSS 9.5)
    trending-vulnerabilitiesServiceNow patches an unauthenticated code-execution sandbox escape in its AI Platform; self-hosted and partner-managed instances are the residual exposure

Where this entity is cited

  • trending-vulnerabilities2

Source distribution

  • support.servicenow.com2 (25%)
  • bleepingcomputer.com1 (12%)
  • euvd.enisa.europa.eu1 (12%)
  • security-hub.ncsc.admin.ch1 (12%)
  • slcyber.io1 (12%)
  • thehackernews.com1 (12%)
  • wid.cert-bund.de1 (12%)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Entries about ServiceNow AI Platform (2)

2026-08-29 · view entry permalink →

CVE-2026-18885 / CVE-2026-18886 / CVE-2026-74820 / CVE-2026-6876, ServiceNow AI Platform: three unauthenticated CVSS 10.0 flaws plus a related Now Platform sandbox escape

ServiceNow's 27 August 2026 advisory (KB3152242) discloses four flaws, found through the vendor's own security research and responsible-disclosure program rather than external report (ServiceNow, 2026-08-27). Three, CVE-2026-18885, CVE-2026-18886 and CVE-2026-74820, are unauthenticated flaws in the ServiceNow AI Platform that ServiceNow's own text classifies as critical: CVE-2026-18885 as code injection letting an unauthenticated user execute arbitrary code and gain access to, or modify, instance data; CVE-2026-74820 as SQL injection letting an unauthenticated user execute arbitrary SQL against the instance's own database; CVE-2026-18886 also as code injection, but described as letting an unauthenticated user create or modify instance data, resulting in privilege escalation (ServiceNow, 2026-08-27). The Hacker News reports the same three at a numeric CVSS4.0 score of 10.0; ServiceNow's own advisory gives only the qualitative "critical" label, never a numeric score (The Hacker News, 2026-08-28). The Hacker News, reporting on the same advisory, assigns each a more specific mechanism: CVE-2026-18885 as a code injection in the GraphQL Composite Data API, CVE-2026-74820 as a SQL injection reached through a dynamic-schema ORDER BY clause, and CVE-2026-18886 as an improper-access-control flaw in the system-configuration image-upload processor enabling privilege escalation, a classification that differs from ServiceNow's own "code injection" description of the same id (The Hacker News, 2026-08-28). All three share the identical CVSS4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H per The Hacker News's reporting, network-reachable, low attack complexity, no privileges, no user interaction, high impact to the vulnerable component and connected systems (The Hacker News, 2026-08-28). A fourth, related flaw, CVE-2026-6876, is a sandbox escape ServiceNow's own text describes as letting an unauthenticated user execute arbitrary code within the Now Platform (ServiceNow, 2026-08-27). The Hacker News reports the CVSS4.0 vector ServiceNow assigned to it in fact specifies PR:L (low privileges required) rather than none (an inconsistency with ServiceNow's own "unauthenticated user" prose) scores it 8.7, and connects it to CVE-2026-6875, a pre-auth ServiceNow sandbox escape Searchlight Cyber reported to ServiceNow on 1 April 2026, with the vendor's own advisory for it published on 13 July 2026 (The Hacker News, 2026-08-28).

ServiceNow deployed the update to hosted instances directly and provided it to partner and self-hosted customers, who must apply it themselves; those customers should verify their instance version against the vendor's fixed-build table, spanning the Xanadu, Yokohama, Zurich and Australia release lines, each with its own minimum hotfix (The Hacker News, 2026-08-28). ServiceNow reports no awareness of exploitation for any of the four flaws, and The Hacker News found no public proof-of-concept for the three maximum-severity flaws as of 28 August 2026 (The Hacker News, 2026-08-28). Because ServiceNow is its own CVE Numbering Authority and none of the four flaws meet NIST's current post-April-2026 enrichment criteria (CISA KEV listing, federal-software impact, or an Executive Order 14028 critical designation), ServiceNow's own severity ratings are the only assessment on record for any of them (The Hacker News, 2026-08-28), a vulnerability-management process that ranks purely on NVD-enriched severity will not see the urgency here.

Detection concept: ServiceNow instance and application audit logs, and GraphQL API access logs, for anomalous or malformed API mutations originating from unauthenticated sessions; database-audit telemetry for dynamic-schema queries carrying non-schema tokens; system-configuration change-audit records for writes not tied to an authenticated administrative session. No public exploit code exists yet, so this is patch-priority guidance rather than an active-exploitation hunt.

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 has remediated a SQL injection vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute arbitrary SQL statements against the instance's underlying database

ServiceNow

A code injection vulnerability in the GraphQL Composite Data API that could enable an unauthenticated user to execute arbitrary code and gain access to, or modify, instance data

An improper access control vulnerability in the system configuration image upload processor that could enable an unauthenticated user to create or modify instance data, resulting in privilege escalation

None of the four flaws appeared in the catalog as of August 28, 2026, leaving ServiceNow's ratings as the only severity assessment on record.

The company said it deployed a security update to hosted instances and provided the update to its partners and self-hosted customers, which leaves organizations that run their own instances to apply the fixes themselves.

The Hacker News 2026-08-28

Builds on: 2026-07-13/servicenow-ai-platform-sandbox-escape-cve-2026-6875

vulnerability29 Aug 04:09Zmulti-sourceOpen finding ↗

2026-07-13 · view entry permalink →

HIGHCVE-2026-6875exploitedupdatedNATOA2

CVE-2026-6875, ServiceNow AI Platform sandbox escape lets an unauthenticated request execute code on the platform (CVSS 9.5)

ServiceNow disclosed CVE-2026-6875, a "Sandbox Escape in ServiceNow AI Platform" rated CVSS 4.0 9.5, in security bulletin KB3137947 published 2026-07-13 (ServiceNow, 2026-07-13; ENISA EUVD, 2026-07-13). Per ServiceNow, the flaw "could enable an unauthenticated user, in certain circumstances, to execute code within the ServiceNow platform", an isolation failure in the AI Platform's code-execution environment. ServiceNow states it "addressed this vulnerability by deploying a security update to hosted instances," provided updates to self-hosted customers and partners, and is "not currently aware of exploitation against ServiceNow instances" (ServiceNow, 2026-07-13). Fixed releases are Zurich Patch 7b/9, Yokohama Patch 12 Hot Fix 1b/13, Australia Patch 2 and Brazil EA/GA. Because hosted instances were remediated server-side by the vendor, the live exposure is narrowed to self-hosted and partner-managed deployments that have not yet applied the update, a population that still includes public-sector and critical-infrastructure operators running ServiceNow ITSM, HR-service-delivery and case-management on-prem or through partners.

This vulnerability, tracked as CVE-2026-6875, could enable an unauthenticated user, in certain circumstances, to execute code within the ServiceNow platform.

We are not currently aware of exploitation against ServiceNow instances.

ServiceNow

Current exploitation status: Actively exploited

NCSC-CH Cyber Security Hub 2026-07-20
Updaterun 2026-07-21T0409Z-intelactionscvesevidenceprioritysectorssourcestagsbody

The unauthenticated ServiceNow AI Platform sandbox escape has moved from "no known exploitation" to confirmed active exploitation. NCSC-CH's 2026-07-20 advisory revision set the item's status to "Actively exploited" (NCSC-CH, 2026-07-20), and BleepingComputer reports attackers "begun exploiting a critical vulnerability (CVE-2026-6875) in the ServiceNow AI Platform," attributing the in-the-wild observation to threat-intelligence firm Defused from around 2026-07-18 (BleepingComputer, 2026-07-20). The mechanism is unchanged from the original entry, an unauthenticated caller reaches unrestricted server-side script execution through the GlideRecord query path, a chain Searchlight Cyber demonstrated where "running any code via eval or new Function will run free from the constraints of the additional sandbox" (Searchlight Cyber, 2026-07-14).

The operational change is entirely one of urgency: exploitation is live, so any self-hosted or partner-managed AI Platform instance still missing the vendor hotfix has crossed from "patch on the normal cycle" to "patch out of band."

vulnerability13 Jul 20:34Zsingle-sourceOpen finding ↗