CVE-2024-4879
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.
- CVSS
- 9.8Critical
- Exploited in the wild
- Yes, in CISA KEV since 29 Jul 2024CISA deadline for US federal agencies: 19 Aug 2024public exploit code
- EPSS
- > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 10 Jul 2024analysed here 12 Nov 2026
Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Weakness
- CWE-1287 Common Weakness
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| ServiceNow Now Platform | < Utah Patch 10 Hot Fix 3< Utah Patch 10a Hot Fix 2< Vancouver Patch 6 Hot Fix 2< Vancouver Patch 7 Hot Fix 3b< Vancouver Patch 8 Hot Fix 4< Vancouver Patch 9< Vancouver Patch 10< Washington DC Patch 1 Hot Fix 2b< Washington DC Patch 2 Hot Fix 2< Washington DC Patch 3 Hot Fix 1< Washington DC Patch 4Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- servicenow:servicenow
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 29 Jul 2024.
- CISA due date
- 19 Aug 2024, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Public exploit code
- Yes: 1 on Exploit-DB · 8 GitHub proofs of concept · 1 Nuclei template
- CISA SSVC
- exploitation active, automatable yes, technical impact totalAssessed by CISA 29 Jul 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Exploit-DB
- ServiceNow Multiple Versions - Input Validation & Template Injectionwebapps, 11 Aug 2025
Nuclei
- ServiceNow UI Macros - Template Injectiondetection template, critical
GitHub proofs of concept
- Brut-Security/CVE-2024-487925 stars
- bigb0x/CVE-2024-487910 stars
- Mr-r00t11/CVE-2024-48794 stars
- NoTsPepino/CVE-2024-4879-CVE-2024-5217-ServiceNow-RCE-Scanning4 stars
and 4 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 10 Jul 2024Published
- 12 Jul 2024First public exploit or proof of concept1 day later
- 29 Jul 2024Added to CISA KEV (exploited in the wild)17 days later
- 29 Jul 2024CISA SSVC assessment: exploitation active1 day later
- 19 Aug 2024CISA remediation due date (US federal agencies)20 days later
- 21 Oct 2025CVE record last updated429 days (about 1 year) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2024-4879 being exploited?
Yes. CVE-2024-4879 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-4879?
CVE-2024-4879 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-4879?
Yes. A fix has been recorded for CVE-2024-4879. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-4879 affect?
CVE-2024-4879 affects servicenow:servicenow. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
4 references in the CVE record, grouped by the tags the record gives them.
Other links (4)
- 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
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-4879
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.