Security readout for executives and security teams
Plain-English summary
A critical flaw in the ServiceNow AI Platform could, under certain circumstances, let an unauthenticated attacker escape intended restrictions and run code within the platform. Successful exploitation could compromise confidentiality, integrity, and availability. ServiceNow has updated hosted instances and supplied updates for self-hosted deployments and partners.
Executive priority
Treat as an immediate patch-verification priority. Require owners to confirm hosted update status and rapidly remediate self-hosted systems. Because the flaw can affect all security objectives without authentication, unresolved or unverifiable deployments should receive focused monitoring and documented risk ownership.
Technical view
CVE-2026-6875 is a network-accessible code-injection issue classified as CWE-94. Its CVSS 4.0 score is 9.5, with high impact across vulnerable and subsequent systems. Exploitation requires high attack complexity but needs no privileges or user interaction. The supplied sources do not identify precise affected versions or technical prerequisites.
Likely exposure
Potential exposure is limited to ServiceNow AI Platform deployments meeting unspecified circumstances. Hosted instances received a deployed security update. Self-hosted customers and partners may remain exposed until they apply the relevant update or upgrade. The supplied affected-version data is insufficient to determine exposure from version numbers alone.
Exploitation context
ServiceNow states it is not currently aware of exploitation against ServiceNow instances, and the CVE is not identified as KEV in the supplied bundle. No public exploit evidence or indicators of compromise are provided. High attack complexity may constrain exploitation, but unauthenticated remote code execution makes credible exposure urgent.
Researcher notes
The record describes a sandbox escape and remote code execution but provides no root-cause detail, affected component path, usable version range, exploitation prerequisites, or indicators. CVSS reports network access, high complexity, no privileges, no interaction, and high impacts. Validation should remain version- and evidence-based rather than attempting exploitation.
Mitigation direction
- Confirm with ServiceNow whether each hosted instance received the deployed security update.
- Apply the relevant ServiceNow security update to every self-hosted AI Platform deployment.
- Upgrade to a patched family release where ServiceNow guidance requires it.
- Obtain the exact applicable patch mapping from ServiceNow KB3137947.
Validation and detection
- Inventory hosted, self-hosted, partner-managed, and non-production ServiceNow AI Platform instances.
- Compare each instance family release and patch level with ServiceNow KB3137947.
- Verify completed updates through deployment records and platform version information.
- Review available platform and security logs for unexplained unauthenticated activity or code execution.
- Escalate uncertain version applicability to ServiceNow support; the supplied version list is not usable.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-6875 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
- 9.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/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:H/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
9.5CriticalVector: CVSS:4.0/AV:N/AC:H/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=KB3137947CVE 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 Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.