CVE-2026-13016

9.3

ServiceNow · ServiceNow AI Platform

A SQL injection vulnerability in the ServiceNow AI Platform allows unauthenticated attackers to execute arbitrary SQL commands, potentially leading to unauthorized data access or modification.

Executive summary

The ServiceNow AI Platform contains a critical SQL injection vulnerability that permits unauthenticated remote attackers to compromise backend database integrity and confidentiality.

Vulnerability

This is a SQL injection vulnerability resulting from improper neutralization of special elements used in an SQL command. The flaw allows an unauthenticated attacker to inject arbitrary queries into the database, bypassing application logic and security constraints.

Business impact

The ability for an unauthenticated attacker to interact directly with the database poses a severe risk to organizational data. With a CVSS score of 9.3, this vulnerability facilitates full unauthorized access to sensitive information stored within the platform and allows for the potential destruction or manipulation of business-critical records.

Remediation

Immediate Action: Administrators must immediately apply the relevant security patches provided by ServiceNow for their specific release train (Yokohama, Zurich, or Australia) as detailed in the official vendor advisory.

Proactive Monitoring: Security teams should review database and application access logs for anomalous query patterns, such as unexpected syntax or large-scale data retrieval attempts originating from unauthorized sources.

Compensating Controls: Deploy a Web Application Firewall (WAF) configured with strict SQL injection protection rules to inspect incoming traffic and block malformed requests targeting the platform endpoints.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the critical nature of this SQL injection vulnerability and the ease of access for unauthenticated attackers, organizations must treat this as a high-priority incident. Ensure all instances are updated to the specified patch levels immediately to prevent potential data breaches or unauthorized administrative control over the database layer.

More ServiceNow CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by Adam Kues - Assetnote, per the CVE Program record.