CVE-2026-6875

Sandbox Escape in ServiceNow AI Platform

No known exploitation. EPSS puts it in the 73rd percentile. Fixed versions are out.

CVSS —Not scored EPSS percentile73rd1.4% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known Fix1 product4 fixed builds listed below

Published 2026-07-13Updated 2026-07-14Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

ServiceNow AI PlatformAffected: < Australia Patch 2Upgrade to: Australia Patch 2Affected: < Yokohama Patch 12 Hot Fix 1bUpgrade to: Yokohama Patch 12 Hot Fix 1bAffected: < Yokohama Patch 13Upgrade to: Yokohama Patch 13Affected: < Zurich Patch 7bUpgrade to: Zurich Patch 7b + 3 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Check whether your ServiceNow AI Platform is on a patched release (compare your currently installed patch level against the fixed versions below: Australia Patch 2, Yokohama Patch 12 Hot Fix 1b, Yokohama Patch 13, Zurich Patch 7b, Zurich Patch 9, Brazil EA, Brazil GA).
If you are not on one of those fixed releases, schedule an urgent update/upgrade to the matching fixed version for your region.
After updating, verify the instance reports as updated successfully and that any recent attempts against the /assessment_thanks.do endpoint are not recurring.
Search your logs and alerts for suspicious requests to the /assessment_thanks.do endpoint and signs of unexpected process/code execution, and escalate any findings to your ServiceNow administrator/vendor immediately.

Usually a quick update

Check it yourselfA free Nuclei and OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

Coverage timeline

4 publishers

ServiceNow RCE vulnerability is being exploited in the wild shortly after disclosure.
as reported · Jul 21, 2026·SecurityWeek summary
Vendor patch released
as reported · Jul 15, 2026·SecurityWeek summary

Sourced from public security reporting — each date is when it was published, not when it happened. 4 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

ServiceNow has addressed a remote code execution vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute code within the ServiceNow platform. ServiceNow addressed this vulnerability by deploying a security update to hosted instances. Relevant security updates have also been provided to ServiceNow self-hosted customers and partners. Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners. We are not currently aware of exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.

In plain language

Written by AI from the record

CVE-2026-6875 is a ServiceNow AI Platform flaw that lets outsiders run code on your system without logging in, and it’s already being exploited—so you should act immediately if you use this product.

CVE-2026-6875 is an unauthenticated remote code execution (RCE) via sandbox escape in the ServiceNow AI Platform; attackers can reach a vulnerable network endpoint to trigger code execution, and exploitation in the wild has been reported.

If you're affected

Full server compromise risk
Service disruption and downtime
Data theft or exposure
Ransomware risk

What is it

This vulnerability is like a “door” in the ServiceNow AI part of your system that can be broken open by anyone on the internet—no login needed. Once opened, attackers can break out of a protective container and run commands on the server, which can lead to complete compromise. Because it’s been actively exploited, you shouldn’t wait for “proof” that it targets your specific company.

Who is affected

This matters if your business uses or hosts the ServiceNow AI Platform (including the AI components covered by this security update). If your setup is reachable from the network, attackers don’t need an account to attempt exploitation. Given reports of active exploitation, treat it as a risk for any exposed ServiceNow AI Platform instance until you confirm you’re on a fixed patch.

How urgent is it

This is RED because attackers are actively exploiting CVE-2026-6875 in the wild. The weakness allows unauthenticated remote code execution through a network-reachable endpoint, and reporting indicates exploitation attempts targeting the /assessment_thanks.do endpoint. Patch availability is confirmed by ServiceNow, so there is no reason to delay upgrade beyond normal emergency change windows.

What to do — in detail

Confirm exposure (fast checks)
- Identify which ServiceNow AI Platform patch line your instance is on and map it to the regional fixed releases.
- If you cannot find the patch level quickly, contact your ServiceNow admin to extract the current AI Platform patch/release details for your region.
Determine whether you are already fixed
- Apply the fixed-version mapping from ServiceNow (as provided):
  - Australia Patch 2
  - Yokohama Patch 12 Hot Fix 1b (or Yokohama Patch 13)
  - Zurich Patch 7b (or Zurich Patch 9)
  - Brazil EA (or Brazil GA)
- If your instance is not on one of these fixed releases, it should be treated as vulnerable.
Upgrade now (priority order)
- Schedule the upgrade to the matching fixed release for your region (use the fixed version list above).
- If you manage both production and non-production, upgrade production first if you can do it safely; otherwise, upgrade environments in a way that allows confirmation before the next tier.
Validate after the change
- Confirm the update completed successfully and the instance reflects the new patch level.
- Review recent activity for suspicious requests to the /assessment_thanks.do endpoint, and confirm you are not seeing repeated exploitation attempts.
Temporary containment if patching is delayed
- Restrict network access to only the necessary sources (e.g., avoid broad internet exposure of the ServiceNow AI Platform features where possible in your environment).
- Increase monitoring around the /assessment_thanks.do endpoint and related execution indicators so you can react quickly if attempts continue.
- Note: these steps do not replace the patch; they are stopgaps until you reach a fixed release.
What to monitor going forward
- Repeated hits to /assessment_thanks.do from unusual sources.
- Alerts indicating abnormal behavior consistent with remote code execution or sandbox escape outcomes.
- Any new errors or instability immediately following suspicious traffic.

CISA due date: not provided in the supplied findings (no KEV listing).

Technical context

Severity/impact (from findings): This is an unauthenticated remote code execution (RCE) issue in the ServiceNow AI Platform caused by a sandbox escape, enabling an attacker to execute arbitrary code on the ServiceNow platform. The attack vector is network-based, and authentication is not required.

Exploitation status: News reporting confirms active exploitation in the wild, with attempts targeting the /assessment_thanks.do endpoint. KEV is not listed in CISA KEV, but exploitation reporting is treated as confirmation.

Attack mechanism: A sandbox escape allows the attacker to go from an initially contained execution context to full code execution on the platform. Reports indicate attackers are using the vulnerable endpoint (/assessment_thanks.do) to reach the same code-execution outcome as prior research.

Patch details: ServiceNow has fixed the vulnerability via region-specific patches/releases, including Australia Patch 2; Yokohama Patch 12 Hot Fix 1b and Yokohama Patch 13; Zurich Patch 7b and Zurich Patch 9; and Brazil EA and Brazil GA.

EPSS note: EPSS was provided as a prediction, but exploitation reporting takes precedence for prioritization.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.