• Home
  • About
  • Locations
  • Contact Us
logologologologo
  • Plan
    • AI Governance & Risk Management
    • Acquisition & VC
    • vCISO
    • Policies & Procedures
    • Strategy & Security Program Creation
    • Risk Management
  • Attack
    • Penetration Testing
    • AI Penetration Testing
    • Mobile Application Penetration Testing
    • Red Teaming
    • Web Application Penetration Testing
    • PTaaS
    • IOT Penetration Testing
  • Defend
    • Office 365 Security
    • HIPAA Compliance
    • PCI Compliance
    • Code Reviews
    • Blockchain Security Analysis
    • Vulnerability Assessments
  • Recover
    • Ransomware Recovery
    • Expert Witness
    • Forensics
  • Learn
    • Resources
    • Penetration Testing Training
    • Blog
  • Tools
    • Wp2shell Checker
    • php2shell checker
  • Instant Quote
✕

Urgent ServiceNow RCE Fixes Teams Need Now

July 20, 2026
Written By: author avatar James Knight
author avatar James Knight
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm’s elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio

The ServiceNow RCE flaw, CVE-2026-6875, lets an unauthenticated attacker escape the platform’s script sandbox and run code on a self-hosted instance. Attackers began probing for it on July 17, 2026, just four days after disclosure. Therefore, teams should patch now, then hunt for new admin accounts and MID Server activity.

What Is CVE-2026-6875?

ServiceNow published advisory KB3137947 on July 13, 2026, and described a remote code execution flaw in the ServiceNow AI Platform. Specifically, an unauthenticated user can run code inside the platform under certain conditions. The flaw scores 9.5 Critical under CVSS v4.0 and maps to CWE-94, code injection. However, the vector also rates attack complexity as high, which explains why exploitation took some skill.

Researchers reported the bug to ServiceNow on April 1, 2026. Within about 24 hours, ServiceNow pushed protections to its hosted instances, and then it shipped patches to self-hosted customers and partners through June. In other words, the July 13 advisory marked public disclosure, not the first fix.

How Does the ServiceNow RCE Sandbox Escape Work?

ServiceNow lets customers run JavaScript inside sandboxed contexts. The attack starts at /assessment_thanks.do, an endpoint that handles survey and assessment responses and needs no login. First, the attacker sends a POST request with a sysparm_assessable_type value that begins with javascript:. Next, the platform evaluates that filter value as code. Then a gadget chain redefines a global function that a script include later calls, and because script include contexts sit outside the sandbox, the attacker’s code runs with platform privileges.

How the ServiceNow RCE chain works from a crafted request to code execution
How the ServiceNow RCE chain works.

This is a classic case of attackers who exploit a public facing application without any credentials. Moreover, the public proof of concept uses one gadget route, while the attackers in the wild used another route to the same primitive. As a result, a single signature cannot cover the whole flaw.

Which ServiceNow Releases Fix the Flaw?

ServiceNow lists ServiceNow RCE fixes for four release families. Meanwhile, it treats any self-hosted or partner-hosted instance on an earlier release as vulnerable. Check your release against this table.

Release familyFixed in
BrazilBrazil EA or Brazil GA
AustraliaAustralia Patch 2
ZurichZurich Patch 7b or Zurich Patch 9
YokohamaYokohama Patch 12 Hot Fix 1b or Yokohama Patch 13
Hosted instancesProtected by ServiceNow since early April 2026

In addition, the update adds Guarded Script, a feature that limits sandboxed code from untrusted inputs, such as filter parameters, to a single simple expression. Because Guarded Script can block legitimate custom scripts, your platform team should test custom logic after the upgrade.

When Did Attacks Begin?

The window between disclosure and attack lasted only days. For that reason, these dates set the start of your log review.

Date (2026)Event
April 1Researchers report the flaw to ServiceNow
Early AprilServiceNow protects hosted instances within about 24 hours
JunePatches reach self-hosted customers and partners
July 13ServiceNow publishes KB3137947 and the CVE record
July 14Researchers publish a technical write up with a working sandbox escape
July 17First reported exploitation attempts against /assessment_thanks.do
July 18Researchers confirm a second gadget chain and a wider wave of attempts
July 20ServiceNow says it sees no evidence the activity relates to hosted instances

What Can Attackers Do After Getting In?

The researchers’ proof of concept went well beyond running one command. For example, it showed that an attacker could create new accounts with admin rights and full read and write access to any table, which gives persistence that survives a patch. It also showed a path to shell commands on connected MID Servers, the proxies that link ServiceNow to on-premises networks.

Workflow data raises the stakes further. Tickets often hold passwords, network diagrams, incident notes, HR records and integration secrets. Consequently, a single ServiceNow RCE compromise can hand an attacker a map of the whole business and a bridge into the internal network.

How Strong Is the Evidence?

Most core ServiceNow RCE facts come straight from the vendor, yet several popular claims rest on single reports. Therefore, this table separates the confirmed points from the reported and open ones.

ClaimStatus
Unauthenticated code execution, CVSS 9.5, fixed releasesConfirmed by ServiceNow advisory KB3137947
Hosted instances protected since early AprilConfirmed by ServiceNow
Exploitation attempts from July 17Reported by one threat intelligence firm
A second gadget chain differs from the public proof of conceptReported by the same firm
First captured requestA probe that tested code execution, not a destructive payload
Admin account creation and MID Server commandsShown in the researchers’ proof of concept, not yet reported in the wild
Confirmed victims or data theftNone published
CISA KEV listingNot found in our research

What Are the Urgent ServiceNow RCE Fixes?

Order matters for every ServiceNow RCE fix, because a patch alone cannot remove an account that an attacker already created. Work through these seven steps from top to bottom.

Fix 1: Verify the Release and Patch

First, inventory every ServiceNow instance and record whether you host it yourself, a partner hosts it, or ServiceNow hosts it. Then upgrade any self-hosted or partner-hosted instance below a fixed release, and do not wait for the monthly maintenance window.

Fix 2: Restrict the Endpoint if You Cannot Patch Today

If a patch must wait, work with ServiceNow or your hosting partner to limit network reach to the affected pre-authentication endpoints. However, treat this step as a stopgap, since it does not remove the flaw.

Fix 3: Do Not Trust WAF Rules Alone

Next, remember that the in the wild gadget chain does not match the public payload. A WAF rule can cut noise, but only the patch closes the sandbox escape.

Fix 4: Hunt the Logs Back to July 13

After that, search for requests to /assessment_thanks.do since July 13, 2026. Focus on sysparm_assessable_type values that contain javascript:, Object.defineProperty, gs.include or Object.extendsObject, and treat any match as a likely compromise.

Fix 5: Audit Admin Accounts and Persistence

Meanwhile, compare every admin account in sys_user against approved users, service accounts and break glass access. Also look for unexpected scheduled jobs, new script includes, role changes and API token use, and disable anything you cannot explain.

Fix 6: Investigate Every MID Server

Likewise, review MID Server command logs, job history, outbound connections and credential use for the exposure window. Treat any MID Server that an exposed instance could reach as involved until the logs prove otherwise, and trim its network access to what it truly needs.

Fix 7: Run Incident Response When You Find a Match

Finally, if an internet facing instance stayed unpatched after July 13, open a formal investigation. Rotate credentials stored in tickets, integration accounts and MID Server configurations, and review Guarded Script results so the fix does not break critical workflows.

Six signals of ServiceNow RCE abuse for log and SIEM hunting
Six signals of abuse.

Which Indicators Should You Hunt For?

Load these reported indicators into your SIEM and web logs. Because ServiceNow RCE attackers can change infrastructure quickly, rely on the endpoint and string patterns more than the single IP address.

POST /assessment_thanks.do sysparm_assessable_type=javascript: Object.defineProperty Object.extendsObject gs.include GlideController evaluateAsObject 146.19.216[.]119

Why Do Workflow Platforms Draw Attackers?

Ultimately, ServiceNow holds the operational truth of a company: who owns each system, which incidents happened, and which vendors connect where. Our 2026 Mid Year Threat Pattern Report tracks the same push toward platforms that sit at the center of business processes, and our analysis of an AI PowerShell Active Directory attack shows how fast attackers turn that kind of access into control.

For that reason, self-hosted platforms need clear owners, version visibility and an emergency patch path. Our team runs penetration testing against web applications and workflow platforms, vulnerability assessments that find unpatched and exposed instances, and a PTaaS platform that keeps that testing continuous.

Key Takeaways

  • CVE-2026-6875 lets an unauthenticated attacker escape the ServiceNow script sandbox through /assessment_thanks.do, with a CVSS v4.0 score of 9.5
  • ServiceNow protected hosted instances in early April and shipped self-hosted patches through June before the July 13 disclosure
  • Attempts began July 17, and attackers used a different gadget chain than the public proof of concept
  • Admin account creation and MID Server commands appear in the proof of concept, so audit both even after patching
  • Patch the ServiceNow RCE flaw first, then hunt logs back to July 13, audit sys_user and scheduled jobs, and review MID Servers

Frequently Asked Questions About the ServiceNow RCE Flaw

What Is the ServiceNow RCE Flaw CVE-2026-6875?

CVE-2026-6875 is a sandbox escape in the ServiceNow AI Platform that lets an unauthenticated attacker run code on a vulnerable instance. It scores 9.5 Critical under CVSS v4.0, and ServiceNow published its advisory, KB3137947, on July 13, 2026.

How Does CVE-2026-6875 Work?

An attacker sends a crafted request to the pre-authentication endpoint /assessment_thanks.do with a filter value that starts with javascript:. The platform evaluates that value, and a gadget chain then breaks out of the script sandbox and reaches code execution.

Are Hosted ServiceNow Instances Exposed?

ServiceNow pushed protections to hosted instances within about a day of the early April report. It also says it has seen no evidence that the July attacks relate to instances it hosts, so self-hosted and partner-hosted instances carry the most risk.

When Did Attacks Begin?

Researchers first saw exploitation attempts on July 17, 2026, four days after public disclosure, and confirmed a wider wave the next day. The first captured request worked as a probe that tested code execution rather than a destructive payload.

Why Do WAF Rules Fall Short?

Attackers reached the same code execution primitive through a different gadget chain than the public proof of concept. As a result, rules written against the published payload can miss real attacks, so the patch remains the only full fix.

Which ServiceNow Releases Fix the Flaw?

The fixed releases are Brazil EA and GA, Australia Patch 2, Zurich Patch 7b or Patch 9, and Yokohama Patch 12 Hot Fix 1b or Patch 13. ServiceNow says any self-hosted instance on an earlier release remains vulnerable.

What Should Teams Do After Patching?

Hunt for requests to /assessment_thanks.do since July 13, audit sys_user for new admin accounts, check scheduled jobs and script includes, and review MID Server command logs. If you find a match, treat the instance as compromised and rotate connected credentials.

author avatar
James Knight Senior Principal, and lead threat intelligence analyst
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm's elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio
Penetration Testing Ransomware Incident Response Threat Intelligence Zero-Day Vulnerability Research
social network icon social network icon
Share
Copyright © Digital Warfare. All rights reserved.
  • Home
  • About
  • Locations
  • Contact Us