CVE-2026-6875

CRITICALPre-NVD 9.59.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.4% (72nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this weekElevated
9.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.5Exploit: Public PoCExposed services: Not assessed

The vendor states that a fix is released ("Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners"), but the CVE record does not name the fixed version — check the vendor's advisory for the fixed release and apply it.

ServiceNow has addressed a remote code execution vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute code within the ServiceNow platform.

ServiceNow addressed this vulnerability by deploying a security update to hosted instances. Relevant security updates have also been provided to ServiceNow self-hosted customers and partners.

Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners. We are not currently aware of exploitation against ServiceNow instances.

We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so.

CVSS v3
9.5
EG Score
9.5CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity95% × 45%
The EG Score, 9.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The vendor states that a fix is released ("Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners"), but the CVE record does not name the fixed version. Check the vendor's advisory for the fixed release and apply it within your standard update timelines.
EPSS PROB
1.4%
EPSS %ILE
72nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The vendor states that a fix is released ("Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners"), but the CVE record does not name the fixed version. Check the vendor's advisory for the fixed release and apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 13, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Vendor states a fix is released — the CVE record does not name the version.
Web page

CVE-2026-6875 - Sandbox Escape in ServiceNow AI Platform - Security - Now Support Portal

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3137947

Vendor Advisories for CVE-2026-6875(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 370 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 270 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 08:40 UTCEG score recompute
  2. 2026-10-14 08:40 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  4. 2026-10-13 03:52 UTCEG score recompute
  5. 2026-10-13 03:52 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  7. 2026-10-12 15:45 UTCEG score recompute
  8. 2026-10-12 05:57 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  9. 2026-10-11 19:30 UTCEG score recompute
  10. 2026-10-11 16:45 UTCEG score recompute
  11. 2026-10-11 14:06 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  22. 2026-10-01 14:12 UTCEG score recompute
  23. 2026-10-01 14:12 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 1.4% · 71st percentile
Show 75 more
  1. 2026-09-28 13:17 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  2. 2026-09-28 09:29 UTCEG score recompute
  3. 2026-09-28 09:29 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  6. 2026-09-24 10:05 UTCEG score recompute
  7. 2026-09-24 10:05 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 78% · 99th percentile
  9. 2026-09-23 11:52 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  10. 2026-09-23 08:06 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  11. 2026-09-23 04:18 UTCEG score recompute
  12. 2026-09-23 04:18 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  13. 2026-09-21 21:09 UTCEPSS rescoreEPSS 78% · 99th percentile
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  15. 2026-09-18 10:06 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  16. 2026-09-18 05:01 UTCEG score recompute
  17. 2026-09-18 05:01 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  18. 2026-09-16 14:08 UTCEPSS rescoreEPSS 78% · 99th percentile
  19. 2026-09-16 05:15 UTCEPSS rescoreEPSS 78% · 99th percentile
  20. 2026-09-14 11:07 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  21. 2026-09-14 07:03 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  22. 2026-09-14 03:17 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  23. 2026-09-13 23:31 UTCEG score recompute
  24. 2026-09-13 23:31 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  25. 2026-09-13 16:30 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  26. 2026-09-13 11:51 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  27. 2026-09-13 07:59 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  28. 2026-09-12 13:26 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  29. 2026-09-12 07:32 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  30. 2026-09-12 01:51 UTCEG score recompute
  31. 2026-09-12 01:51 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 78% · 99th percentile
  33. 2026-09-10 09:35 UTCEPSS rescoreEPSS 78% · 99th percentile
  34. 2026-09-08 01:54 UTCEG score recompute
  35. 2026-09-08 01:54 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 78% · 99th percentile
  37. 2026-09-06 13:49 UTCEG score recompute
  38. 2026-09-06 13:49 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 78% · 99th percentile
  40. 2026-09-06 05:23 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  41. 2026-09-06 01:36 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  42. 2026-09-05 21:24 UTCEG score recompute
  43. 2026-09-05 21:24 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  44. 2026-09-05 15:31 UTCEPSS rescoreEPSS 78% · 99th percentile
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 78% · 99th percentile
  46. 2026-08-30 23:59 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  47. 2026-08-30 20:11 UTCEG score recompute
  48. 2026-08-30 20:11 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  49. 2026-08-30 19:17 UTCEPSS rescoreEPSS 78% · 99th percentile
  50. 2026-08-30 16:25 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  51. 2026-08-30 10:59 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  52. 2026-08-30 05:28 UTCEG score recompute
  53. 2026-08-30 05:28 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 78% · 99th percentile
  55. 2026-08-28 21:42 UTCEPSS rescoreEPSS 78% · 99th percentile
  56. 2026-08-28 02:31 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  57. 2026-08-27 21:47 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  58. 2026-08-27 18:01 UTCEG score recompute
  59. 2026-08-27 18:01 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  60. 2026-08-27 14:00 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  61. 2026-08-27 03:59 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  62. 2026-08-27 00:13 UTCEG score recompute
  63. 2026-08-27 00:13 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  64. 2026-08-26 14:47 UTCEPSS rescoreEPSS 78% · 99th percentile
  65. 2026-08-26 12:50 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  66. 2026-08-26 07:58 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  67. 2026-08-26 02:21 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  68. 2026-08-25 19:16 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  69. 2026-08-25 14:50 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  70. 2026-08-25 11:05 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  71. 2026-08-25 07:17 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  72. 2026-08-25 03:29 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  73. 2026-08-24 23:44 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL
  74. 2026-08-24 19:58 UTCEG score recompute
  75. 2026-08-24 19:58 UTCGHSA enrichmentGHSA-8jw2-7qp4-v2jj · GitHub severity CRITICAL

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Nucleihttp/cves/2026/CVE-2026-6875.yaml
    Published Jul 22, 2026

    ServiceNow AI Platform - Pre-Auth JavaScript Sandbox Escape RCE

    Open source ↗
  • GitHub PoCtc4dy/CVE-2026-6875-PoC-Exploit
    Published Jul 21, 2026

    CVE-2026-6875 ServiceNow Pre-Auth RCE Framework 🔥 JS Injection → Sandbox Escape → RCE → Root. Features: --detect, --exec, reverse/interactive shell, batch threading, WAF bypass, persistence, lateral movement, credential dump, fileless exec, clean tracks. 🛡️ CVSS 9.5 actively exploited. Authorized & Legal use only. Stay Legal. 🔒

    Open source ↗

Frequently asked(5)

What is CVE-2026-6875?
CVE-2026-6875 is a critical-severity vulnerability; its CVE record was published on July 13, 2026. ServiceNow has addressed a remote code execution vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute code within the ServiceNow platform. ServiceNow addressed this vulnerability by deploying a…
When was the CVE record for CVE-2026-6875 published?
The CVE record for CVE-2026-6875 was published on July 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-6875 actively exploited?
CVE-2026-6875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6875?
CVE-2026-6875 has a CVSS base score of 9.5 (the CNA's own assessment, by sn; NVD's own analysis pending).
How do I remediate CVE-2026-6875?
The CVE record for CVE-2026-6875 states that the vendor has released a fix: "Further, the vulnerability is addressed in the listed patches and family releases, which have been made available to hosted and self-hosted customers, as well as partners." The record does not name the fixed version: check the vendor's advisory for the fixed release and update to it. The vendor advisories EchelonGraph has for CVE-2026-6875 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6875

Explore →

Is Your Infrastructure Affected by CVE-2026-6875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.