Security readout for executives and security teams
Plain-English summary
A critical flaw in the ServiceNow AI Platform could let an unauthenticated internet user, under unspecified circumstances, access or change instance data by manipulating database queries. ServiceNow says hosted instances received an update and reports no known malicious exploitation. Partner-managed and self-hosted customers should promptly confirm they installed the provided update or upgraded to a patched release.
Executive priority
Treat this as an immediate remediation and assurance task because successful exploitation could expose or alter critical instance data without authentication. Require confirmation that every hosted, partner-managed, and self-hosted deployment is patched. Escalate internet-accessible or remediation-uncertain instances first, while noting that current sources report no known malicious exploitation.
Technical view
CVE-2026-74820 is a CWE-89 SQL injection involving a dynamic schema ORDER BY clause. Its CVSS 4.0 score is 10.0, reflecting network access, low complexity, no authentication or user interaction, and potentially high confidentiality, integrity, and availability impacts. The supplied sources do not identify precise affected versions, required circumstances, indicators, or patched release numbers.
Likely exposure
Potential exposure is limited to vulnerable ServiceNow AI Platform instances meeting unspecified circumstances. Hosted instances should have received ServiceNow's deployed update, but organizations should verify. Partner-managed and self-hosted instances remain concerning if the provided update or a patched release has not been applied. The supplied version list is not usable for determining exposure.
Exploitation context
ServiceNow states it is not currently aware of malicious exploitation, and the CVE is not identified as a CISA KEV entry in the supplied bundle. Nevertheless, unauthenticated network reachability, low stated complexity, and possible arbitrary SQL execution make unpatched exposure highly consequential. No public exploit, attack indicators, or observed campaigns are established by these sources.
Researcher notes
The title attributes the injection to a dynamic schema ORDER BY clause, but the sources provide no affected endpoint, request structure, database details, or triggering conditions. Do not infer these details. Exact affected and fixed versions are absent, and the repeated zero values are not actionable version data. Validation should therefore rely on ServiceNow's KB and deployment evidence.
Mitigation direction
- Confirm hosted instances received ServiceNow's deployed security update.
- Apply ServiceNow's provided update to partner-managed or self-hosted instances promptly.
- Alternatively, upgrade affected deployments to a patched release identified in vendor guidance.
- Restrict unnecessary external access while remediation status remains uncertain.
- Follow ServiceNow KB3152242 for authoritative release and remediation details.
Validation and detection
- Inventory ServiceNow AI Platform instances and record each hosting model.
- Verify installed build and update status against ServiceNow KB3152242.
- Confirm remediation through deployment records and platform update history.
- Review logs for suspicious unauthenticated requests and unusual database activity.
- Investigate unexpected data access, modification, or integrity changes.
- Document exceptions where precise version applicability remains unresolved.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-74820 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——SNVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3152242CVE reference, SN
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.