CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

ServiceNow AI Platform

product · product:servicenow-ai-platform

Coverage
2
first 2026-07-13 → last 2026-09-30
Latest activity
2026-08-29
ServiceNow patches four unauthenticated flaws in its AI Platform and Now Platform, three of them maximum…
Peak priority
high
2 high
Targets
public-sector
sectors: public-sector, finance, healthcare
Sources cited
8
7 hosts

Action items (1)

Do-now tasks recorded on the entries about ServiceNow AI Platform, newest first. Check the date before acting on an older one.

  • Apply the fixed release for your family listed in ServiceNow security bulletin KB3137947 (Zurich Patch 7b or 9, Yokohama Patch 12 Hot Fix 1b or Patch 13, Australia Patch 2, Brazil EA or GA) to every self-hosted or partner-managed ServiceNow AI Platform instance now. Exploitation attempts have been reported since 2026-07-17, and self-hosted instances are the ones ServiceNow did not fix itself.
    2026-07-13CVE-2026-6875

Defender insights

What each entry about ServiceNow AI Platform tells a defender to do, newest first.

2026-07-13HIGHexploitedServiceNow patches an unauthenticated code-execution sandbox escape in its AI Platform; self-hosted and partner-managed instances are the residual exposure

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
ATT&CK techniques (2 across 2 tactics)

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

  • Initial AccessExploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter: JavaScript

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 ↗

Execution TA0002

T1059.007Command and Scripting Interpreter: JavaScript×1

Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.

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

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: ServiceNow patches an unauthenticated code-execution sandbox escape in its AI Platform…

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," and provided updates to self-hosted customers and partners (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 (ServiceNow, 2026-07-13).

Contradiction: ServiceNow's advisory states that it is "not currently aware of exploitation against ServiceNow instances" (ServiceNow, 2026-07-13). BleepingComputer reported on 2026-07-20 that the advisory still said so and that ServiceNow had yet to flag the flaw as actively abused, and a ServiceNow spokesperson told it that, based on its investigation to date, it had not observed evidence that the activity is related to instances ServiceNow hosts (BleepingComputer, 2026-07-20). Defused reports in-the-wild exploitation attempts since 2026-07-17 (BleepingComputer, 2026-07-20), and NCSC-CH gives the exploitation status as actively exploited, citing that reporting (NCSC-CH, 2026-07-20).

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 reported active exploitation. NCSC-CH's advisory of 2026-07-20 gives the exploitation status as "Actively exploited" and cites news coverage of claims of active exploitation (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, which saw first attempts on 2026-07-17 (BleepingComputer, 2026-07-20). Searchlight Cyber's analysis shows the mechanism: an unauthenticated caller gets server-side JavaScript evaluated through a GlideRecord query on a pre-authentication page, then escapes the script sandbox by obtaining the Function constructor through Class.create.constructor and running it during a gs.include() script-include evaluation, which ServiceNow runs without the sandbox's constraints (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 fixed release has crossed from "patch on the normal cycle" to "patch out of band." ServiceNow's hosted/SaaS estate is already remediated, so exposure concentrates in on-prem and MSP-run deployments, which should be inventoried first. The hunt telemetry is in the takeaway above.

Correctionrun 2026-09-30T0639Z-auditsummarysourcing_noteverificationbodytechniquesactionscves

The summary above said no exploitation was known. BleepingComputer reports Defused observing first exploitation attempts on 2026-07-17, and NCSC-CH's advisory of 2026-07-20 flags the CVE as actively exploited, citing that news coverage (NCSC-CH, 2026-07-20; BleepingComputer, 2026-07-20). ServiceNow's advisory states that it is not currently aware of exploitation against ServiceNow instances (ServiceNow, 2026-07-13), and its spokesperson told BleepingComputer that it had not observed evidence that the activity relates to instances ServiceNow hosts (BleepingComputer, 2026-07-20).

The takeaway above also said no exploitation discriminator existed. The observed payloads hit the pre-authentication sink /assessment_thanks.do that Searchlight Cyber documented, by a different route than its published proof of concept (BleepingComputer, 2026-07-20). Searchlight's own route abuses javascript: values in GlideRecord query parameters and gs.include() evaluation (Searchlight Cyber, 2026-07-14). The sandboxed script cannot call eval or new Function, which the sandbox forbids. It reaches the Function constructor indirectly, through Class.create.constructor, and a gs.include() evaluation outside the sandbox then runs it (Searchlight Cyber, 2026-07-14). Its example request is a GET, not a POST.

ServiceNow addressed hosted instances starting in April. 2026-07-13 is the release date of the self-hosted updates, and KB3137947 is the security bulletin listing the fixed releases, not a hotfix (BleepingComputer, 2026-07-20; ServiceNow, 2026-07-13).

vulnerability13 Jul 20:34Zmulti-sourceOpen finding →

Co-occurring entities

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

Where this entity is cited

  • Vulns2

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%)