ServiceNow just dropped patches for four critical security flaws in its AI Platform. Three of them have a CVSS score of 10.0, the highest possible rating. In some cases, attackers don't even need credentials to exploit them.

The company rolled out updates for its hosted instances. It also provided patches to partners and self-hosted customers. If you run your own ServiceNow instance, you need to apply these fixes yourself.

If you use ServiceNow, this affects you. Let me break down what's happening and how to protect your systems.

Quick Summary

The Vulnerabilities

CVE-2026-18885 (CVSS 10.0)

Code Injection in the GraphQL Composite Data API. The vulnerability allows an attacker without any authentication to run arbitrary code, which allows access or modification of instance data.

CVE-2026-18886 (CVSS 10.0)

An access control weakness in the configuration image upload processor. An attacker without any authentication can modify the instance data, which allows privilege escalation.

CVE-2026-74820 (CVSS 10.0)

A SQL injection vulnerability reached through a dynamic schema ORDER BY clause. An attacker could execute arbitrary SQL statements against the database.

CVE-2026-6876 (CVSS 8.7)

A sandbox escape in the Now Platform. Could allow an unauthenticated user to execute arbitrary code.

Affected Versions

What's Being Exploited?

The advisory follows CVE-2026-6875, a sandbox escape reported by Searchlight Cyber on April 1, 2026. ServiceNow published the advisory on July 13.

Exploitation Activity:

Threat intelligence firm Defused observed in-the-wild exploitation of CVE-2026-6875. The captured payload matched Searchlight Cyber's published PoC exploit.

ServiceNow's Response:

"We are aware of a cybersecurity company's recent publication regarding exploitation activity associated with CVE-2026-6875. Based on our investigation to date, we have not observed evidence that this activity is related to instances that ServiceNow hosts."

What's Not Being Exploited

ServiceNow said it's not aware of exploitation for the four new flaws. The Hacker News found no public exploit code for the three maximum-severity flaws as of August 28, 2026.

The CVSS Ratings

The 10.0 ratings are ServiceNow's own. Since April 15, 2026, NIST has enriched only vulnerabilities in CISA's KEV catalog, affecting federal software, or designated critical under Executive Order 14028.

None of the four flaws appeared in the catalog as of August 28, 2026. ServiceNow's ratings are the only severity assessment on record.

What You Should Do

1. Apply the Patches

If you run a self-hosted ServiceNow instance, apply the patches immediately.

2. Check Your Version

Verify which release you're running. The affected versions are listed above.

3. Monitor for Suspicious Activity

• Look for unusual GraphQL API calls
• Watch for unexpected SQL queries
• Monitor for unauthorized access attempts

4. Follow ServiceNow's Guidance

ServiceNow is working directly with customers who need assistance applying the patches.

The Bottom Line

ServiceNow patched four critical flaws in its AI Platform. Three have CVSS scores of 10.0. Attackers could exploit them without credentials.

What You Need to Know:

Actions Required:

• Install the patches right away
• Identify your version number
• Look out for any unusual behavior
• Adhere to the recommendations from ServiceNow

FAQ Section

What are the ServiceNow AI Platform vulnerabilities?

Four critical flaws in the ServiceNow AI Platform. The three vulnerabilities are assigned a CVSS score of 10.0. They allow remote code execution, privilege escalation, and SQL injection.

Which versions are affected?

Xanadu, Yokohama, Zurich, and Australia releases are affected. Specific patch versions are listed above.

Are they being exploited?

ServiceNow is not aware of exploitation for the four new flaws. However, a related sandbox escape (CVE-2026-6875) has seen exploitation activity.

What should I do?

Apply the patches immediately. Check your version. Monitor for suspicious activity.

What about hosted instances?

ServiceNow deployed the security update to hosted instances. Fixes have to be applied by the self-hosted customers.

Source: The Hacker News