dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-6875

CRITICAL · 9.5 CVSS v4.0 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 5 outlets this week · latest 4w ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ServiceNow AI platform contains a critical remote code execution vulnerability (CVSS 9.5) enabling unauthenticated attackers to execute arbitrary code within the platform under certain conditions. The vulnerability was addressed via security updates deployed to hosted instances and patches provided to self-hosted customers and partners.

MitigationApply the provided security patches or upgrade to the patched family releases as specified in ServiceNow's security advisory; prioritize immediate deployment given the critical severity and unauthenticated attack vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ServiceNow instance version
    Navigate to System Diagnostics > System Version or check the login page footer for the build version. Alternatively, query the 'sys_properties' table for 'glide.version' or use the 'info.do' endpoint.
    Affected if The installed version matches or predates the patched releases mentioned in ServiceNow's security advisory for this CVE
  2. Verify AI platform module status
    Check if AI Search, AI Risk, or other AI-related plugins are activated. Go to System Definition > Plugins and search for 'AI' related plugins. Look for 'AI Search', 'AI Risk', 'Predictive Intelligence', or similar AI modules.
    Affected if AI platform plugins/modules are installed and active, as the vulnerability affects the ServiceNow AI platform component
  3. Check for unauthorized script execution
    Review system logs in 'System Logs > All' or query the 'sys_script' table for recently created or modified script includes, business rules, or scheduled jobs that appear unfamiliar. Check 'sys_audit' table for unusual create/modify events on executable objects.
    Affected if Unfamiliar scripts, business rules, or scheduled jobs exist that were not created by authorized administrators, indicating potential exploitation
  4. Inspect outbound network connections
    Review 'System Diagnostics > Connection Logs' or check firewall/proxy logs for unexpected outbound connections from the ServiceNow server to unknown external addresses, particularly those associated with command-and-control behavior.
    Affected if Unexpected outbound network connections are observed originating from the ServiceNow instance

An unpatched ServiceNow instance with AI platform features enabled is likely affected; verify version against ServiceNow's advisory and confirm no unauthorized script modifications or unusual network activity has occurred.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the provided security patches or upgrade to the patched family releases as specified in ServiceNow's security advisory; prioritize immediate deployment given the critical severity and unauthenticated attack vector.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6875 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data