CVE-2026-6876

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 10.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

ServiceNow has remediated a sandbox escape security issue that was identified in the ServiceNow AI Platform. This security issue could allow an unauthenticated user to execute arbitrary code within the ServiceNow AI Platform, potentially leading to more access to the ServiceNow AI Platform than intended. 

ServiceNow deployed a security update to hosted instances and ServiceNow provided the update to our partners and self-hosted customers. We are not currently aware of malicious 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
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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

August 27, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Oct 14, 2026
No fix on record yet.
Web page

August 2026 CVE Advisory Notification - Security - Now Support Portal

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

Vendor Advisories for CVE-2026-6876(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 184× 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 315 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 215 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-6876?
CVE-2026-6876 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. ServiceNow has remediated a sandbox escape security issue that was identified in the ServiceNow AI Platform. This security issue could allow an unauthenticated user to execute arbitrary code within the ServiceNow AI Platform, potentially leading to more access to the ServiceNow AI Platform than…
When was the CVE record for CVE-2026-6876 published?
The CVE record for CVE-2026-6876 was published on August 27, 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 September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-6876 actively exploited?
CVE-2026-6876 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6876?
CVE-2026-6876 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6876?
No fix for CVE-2026-6876 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-6876 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-6876?

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