CVE-2024-4879 ServiceNow Improper Input Validation Vulnerability
ServiceNow Utah, Vancouver, and Washington DC Now Platform releases contain a jelly template injection vulnerability in UI macros. An unauthenticated user could exploit this vulnerability to execute code remotely.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 29 Jul 2024.
- Rated Critical severity (CVSS 9.8, scored by Vendor).
- It has been in the catalogue for 830 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
ServiceNow has addressed an input validation vulnerability that was identified in Vancouver and Washington DC Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. ServiceNow applied an update to hosted instances, and ServiceNow released the update to our partners and self-hosted customers. Listed below are the patches and hot fixes that address the vulnerability. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible.
Affected Versions
| Product | Versions |
|---|---|
| ServiceNow Now Platform | before Utah Patch 10 Hot Fix 3 before Utah Patch 10a Hot Fix 2 before Vancouver Patch 6 Hot Fix 2 before Vancouver Patch 7 Hot Fix 3b before Vancouver Patch 8 Hot Fix 4 before Vancouver Patch 9 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for ServiceNow Utah, Vancouver, and Washington DC Now Platform. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-4879 and every other exploited flaw on the list.
Sources
- CISA Known Exploited Vulnerabilities catalogue
- NVD: CVE-2024-4879
- CVE record: CVE-2024-4879
- FIRST EPSS
- support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1645154
- support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644293
- darkreading.com/cloud-security/patchnow-servicenow-critical-rce-bugs-active-exploit
