Skip to main content
Mallory
← Back to News
ai-platform-securitycloud-service-vulnerabilitywidely-deployed-product-advisoryinternet-facing-service-vulnerability

Critical ServiceNow AI Platform Sandbox Escape Enables Unauthenticated RCE

Emerging Technology Risk · 22 sources · Updated 4mo ago · First seen Jul 13, 2026

Critical ServiceNow AI Platform Sandbox Escape Enables Unauthenticated RCE

ServiceNow disclosed and remediated CVE-2026-6875, a critical sandbox escape in its AI Platform that can allow unauthenticated remote code execution in certain circumstances. The vulnerability affects both hosted and self-hosted ServiceNow environments, carries a CVSS 4.0 score of 9.5, and was published in advisory KB3137947. ServiceNow said it has already deployed security updates to hosted instances and issued patched family releases and updates for self-hosted customers and partners.

The company said it is not currently aware of active exploitation, but warned that successful compromise could let attackers execute code within the ServiceNow platform, disrupt workflows, access sensitive data, modify records, and enable follow-on malicious activity. To reduce near-term exploit risk, ServiceNow limited public technical details while directing customers to promptly apply the relevant updates or upgrade to patched releases, including fixes for the Brazil, Australia, Zurich, and Yokohama release families.

New surface, new adversariesTrack how attackers are adapting to this technology.
Track this risk
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

7 events · Apr 1, 2026 – Jul 18, 2026
  1. Jul 18, 20264mo ago

    PoC exploit details for CVE-2026-6875 are publicly disclosed

    A new report says technical details and proof-of-concept exploit code for CVE-2026-6875 were publicly disclosed, increasing the risk of broader exploitation of the ServiceNow AI Platform flaw. The report describes attacks against the pre-authentication /assessment_thanks.do endpoint using crafted payloads to achieve sandbox escape and remote code execution.

    CVE-2026-6875 PoC Disclosed: ServiceNow Sandbox Escape RCE
  2. Jul 18, 20264mo ago

    Defused revises CVE-2026-6875 exploitation assessment

    After initially reporting that in-the-wild exploitation used a different sandbox-escape path, Defused later corrected its assessment and said the captured payload was identical to Searchlight Cyber’s published proof-of-concept. The update suggested some observed activity may have come from researchers rather than threat actors.

    Exploitation of ServiceNow Vulnerability Seen Days After Disclosure - SecurityWeek
  3. Jul 17, 20264mo ago

    Defused observes active exploitation of CVE-2026-6875

    Defused reported that attackers began exploiting CVE-2026-6875 in the wild only days after ServiceNow released patches. The attacks targeted the /assessment_thanks.do pre-authentication sink and used a different sandbox-escape path than the previously published proof of concept.

    Critical ServiceNow code execution flaw now exploited in attacks
  4. Jul 14, 20264mo ago

    ServiceNow introduces Guarded Script sandbox hardening

    Following CVE-2026-6875, ServiceNow introduced stricter sandbox protections called Guarded Script to reduce the likelihood of future sandbox escapes. The change is described as an additional hardening measure beyond the immediate mitigation and released patches.

    Smashing the ServiceNow Sandbox - Pre Authentication RCE › Searchlight Cyber
  5. Jul 13, 20264mo ago

    ServiceNow deploys fixes for hosted and self-hosted environments

    ServiceNow said it addressed CVE-2026-6875 by deploying security updates to hosted instances and releasing patched family versions and updates for self-hosted customers and partners. The remediation covered affected releases including Brazil, Australia, Zurich, and Yokohama.

    CVE-2026-6875 - Sandbox Escape in ServiceNow AI Platform
  6. Jul 13, 20264mo ago

    ServiceNow publishes advisory for CVE-2026-6875

    On 2026-07-13, ServiceNow published advisory KB3137947 disclosing CVE-2026-6875, a critical sandbox escape in its AI Platform that could enable unauthenticated remote code execution. The company said it was not aware of active exploitation at the time.

    CVE-2026-6875 - Sandbox Escape in ServiceNow AI Platform
  7. Apr 1, 20268mo ago

    ServiceNow receives CVE-2026-6875 report and applies cloud-side mitigation

    According to the new reference, researchers reported CVE-2026-6875 to ServiceNow on 2026-04-01. The vendor reportedly deployed an immediate mitigation for cloud instances within 24 hours, ahead of the broader July advisory and fixes.

    Public PoC released for Critical ServiceNow Sandbox RCE Vulnerability
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

2 linked
ServicenowServicenow Ai Platform

Organizations

1 linked
Servicenow

Observables

1 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Follow how adversaries are adapting to this technology, and where it touches your stack today.
Track This Risk
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.