CyberSecBulletin
CVE-2026-6876NVD status: Awaiting Analysis

ServiceNow AI Platform: Improper Control of Generation of Code

Published Updated By the CyberSecBulletin desk

CVE-2026-6876 is a critical-severity improper control of generation of code vulnerability in ServiceNow AI Platform from ServiceNow, with a CVSS 4.0 base score of 10.0 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions Xanadu Patch 11 Hot Fix 7a, Yokohama Patch 12 Hot Fix 3b, Yokohama Patch 13 Hot Fix 4 as the first without the flaw, so updating ServiceNow AI Platform to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.68% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update ServiceNow AI Platform to Xanadu Patch 11 Hot Fix 7a or Yokohama Patch 12 Hot Fix 3b or Yokohama Patch 13 Hot Fix 4 or Zurich Patch 7b Hot Fix 3, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ServiceNowServiceNow AI Platformbefore Xanadu Patch 11 Hot Fix 7a; before Yokohama Patch 12 Hot Fix 3b; before Yokohama Patch 13 Hot Fix 4; before Zurich Patch 7b Hot Fix 3; before Zurich Patch 8 Hot Fix 5; before Zurich Patch 9 Hot Fix 6; before Zurich Patch 10 Hot Fix 2m (m-branch); before Zurich Patch 10 Hot Fix 3 (standard); and 7 more rangesXanadu 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, Zurich Patch 9 Hot Fix 6

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Attack requirements
NoneThe attack does not depend on a particular deployment or configuration.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Confidentiality (vulnerable system)
HighSerious loss of confidentiality on the vulnerable system.
Integrity (vulnerable system)
HighSerious loss of integrity on the vulnerable system.
Availability (vulnerable system)
HighSerious loss of availability on the vulnerable system.
Confidentiality (other systems)
HighSerious loss of confidentiality on systems beyond the vulnerable one.
Integrity (other systems)
HighSerious loss of integrity on systems beyond the vulnerable one.
Availability (other systems)
HighSerious loss of availability on systems beyond the vulnerable one.

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (servicenow.com).

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Control of Generation of Code

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

How developers prevent this class of flaw

  • Refactor your program so that you do not have to dynamically generate code.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

More Improper Control of Generation of Code vulnerabilities (CWE-94)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in ServiceNow AI Platform

All ServiceNow AI Platform vulnerabilities

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.