Latest / The Digital Warfare Podcast / Digital Warfare Podcast Daily Brief #133 July 20, 2026
Transcript
- Digital Warfare: You're listening to the Digital Warfare Podcast. Today we are covering a critical ServiceNow vulnerability that turns a restricted scripting environment into a potential path toward full platform compromise. And the key issue is not simply remote code execution, it is what ServiceNow already connects to. The vulnerability is tracked as CVE-2026-6875. It affects the ServiceNow AI platform and allows an unauthenticated attacker to escape a restricted JavaScript sandbox and execute code inside a vulnerable ServiceNow instance. A public proof of concept is now available. That changes the risk immediately. ServiceNow confirmed the issue and deployed protections to hosted environments. Updates have also been released for self-hosted customers and partners. The company says it is not aware of active exploitation. But once working exploit details become public, the window between research and operational abuse begins to shrink. Here is how the vulnerability works. ServiceNow applications use an interface called GlideRecord to query and process information stored in platform tables. Researchers discovered that certain application paths available before authentication passed user-controlled input into GlideRecord query functions. A specially crafted JavaScript query could cause attacker-supplied code to be evaluated before the query completed. ServiceNow anticipated this risk. Untrusted expressions were supposed to run inside a restricted script sandbox. That sandbox blocked dangerous capabilities such as direct evaluation, dynamic function creation, arbitrary function declarations, and access to sensitive Java classes. But the protection was incomplete. Researchers found that the gs.include function could load script libraries into a less restricted execution context. By manipulating global JavaScript objects and properties used by those included scripts, an attacker could transition from the restricted sandbox Into a more privileged scripting environment, the attacker does not break the sandbox directly. They move execution into a context where the sandbox no longer controls it. Once outside, the consequences become serious. An attacker may be able to access ServiceNow tables, read sensitive records, create administrator accounts, perform privileged platform actions, and interact with configured MID servers. That last point is critical. MID servers connect ServiceNow Cloud instances to internal enterprise systems. They often sit inside trusted networks and communicate with directories, databases, infrastructure tools, discovery services, and business applications. If an attacker compromises the ServiceNow instance and reaches those connected systems, the incident can move beyond the platform itself. The workflow system becomes a bridge into the enterprise. That is why this vulnerability matters. ServiceNow frequently manages IT operations, incident response. Employee workflows, asset records, identity processes, customer service, and sensitive business data. A platform compromise may expose much more than tickets. It may expose how the organization operates. Researchers reported the issue to ServiceNow on April 1, 2026. ServiceNow introduced an initial cloud-side mitigation within 24 hours by preventing changes to critical JavaScript functions, then released broader fixes addressing the underlying sandbox weakness. The company also introduced guarded script protections. Simple expressions and basic function calls can still operate normally. More complex server-side logic involving variables, loops, assignments, conditionals, or multiple statements must be moved into controlled script includes. For defenders, the response should be immediate. First, confirm whether your service now instance is running a fixed release. The vulnerability is addressed in Brazil EA and GA, Australia Patch 2, Zurich Patch 7B and Patch 9, and Yokohama Patch 12. Hotfix 1B and patch 13. Second, review exposed pre-authentication application paths and custom scripts that process user-controlled query values. Third, examine administrator creation, unusual table access, unexpected scripted activity, and suspicious MID server communication. Fourth, review the incompatible guarded scripts list after upgrading so security changes do not silently break critical workflows. And finally, treat ServiceNow as privileged infrastructure. It should receive the same hardening, monitoring, access control, and incident response priority as identity platforms and cloud management systems. The strategic lesson is direct. A sandbox is only effective if every execution path remains inside it. And when a workflow platform connects cloud services to internal systems, escaping that sandbox can become the first step toward compromising the business behind it. This has been your Digital Warfare Daily Brief. Stay secure. We'll see you tomorrow.