CVE-2024-4879
CVE-2024-4879 is a critical-severity vulnerability in Servicenow with a CVSS 3.x base score of 9.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2024-07-29). The underlying weakness is classified as CWE-1287.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- CVSS v4: 9.3
- EPSS exploit prediction: 100% (100th percentile)
- Actively exploited: Yes — listed in CISA KEV (added 2024-07-29)
- EU (EUVD) id: EUVD-2024-44451
- EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2024-07-29)
- Weakness: CWE-1287
- Affected product: Servicenow
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is 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.
- How severe is CVE-2024-4879?
- CVE-2024-4879 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2024-4879 being actively exploited?
- Yes. CVE-2024-4879 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-07-29, which means active exploitation has been confirmed. It should be prioritised for remediation.
- What products are affected by CVE-2024-4879?
- CVE-2024-4879 primarily affects Servicenow. In total, 90 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2024-4879?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
- Does CVE-2024-4879 have an EU (EUVD) identifier?
- Yes. CVE-2024-4879 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-44451. It is also flagged as exploited in the EUVD (since 2024-07-29).
- When was CVE-2024-4879 published?
- CVE-2024-4879 was published on 2024-07-10 and last updated on 2026-06-17.
References
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644293
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1645154
- https://www.darkreading.com/cloud-security/patchnow-servicenow-critical-rce-bugs-active-exploit
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-4879
Affected products (90)
- cpe:2.3:a:servicenow:servicenow:utah:-:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:early_availability:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_1_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_1_hotfix_1a:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_1_hotfix_1b:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_1_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_10:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_10_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_10_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_10a:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_10a_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_2_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_2_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_2_hotfix_3:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_2_hotfix_4:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_3:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_3_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_3_hotfix_1b:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_2a:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_2b:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_3:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_3b:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_4:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_4b:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_4_hotfix_5:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_5:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_5_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_6:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_6_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_6_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_7:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_7_hotfix_1:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_7_hotfix_2:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_7a:*:*:*:*:*:*
- cpe:2.3:a:servicenow:servicenow:utah:patch_7b:*:*:*:*:*:*
More vulnerabilities in Servicenow
- CVE-2022-43684 — Critical (CVSS 9.9): ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow…
- CVE-2024-8923 — Critical (CVSS 9.8): ServiceNow has addressed an input validation vulnerability that was identified in the Now Platform. This vulnerability…
- CVE-2024-5217 — Critical (CVSS 9.8): ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and…
- CVE-2018-7748 — High (CVSS 8.8): report_viewer.do in ServiceNow Release Jakarta Patch 8 and earlier allows remote attackers to execute arbitrary code…
- CVE-2024-8924 — High (CVSS 7.5): ServiceNow has addressed a blind SQL injection vulnerability that was identified in the Now Platform. This…
- CVE-2022-46389 — Medium (CVSS 6.1): There exists a reflected XSS within the logout functionality of ServiceNow versions lower than Quebec Patch 10 Hotfix…
All CVEs affecting Servicenow →
Other CWE-1287 vulnerabilities
- CVE-2024-51550 — Critical (CVSS 10.0): Data Validation / Data Sanitization vulnerabilities in Linux allows unvalidated and unsanitized data to be injected in…
- CVE-2024-6298 — Critical (CVSS 10.0): Unauthorized file access in WEB Server in ABB ASPECT - Enterprise v3.08.01; NEXUS Series v3.08.01 ; MATRIX Series…
- CVE-2026-44935 — Critical (CVSS 9.9): Missing validation of "valuesFrom" references in Helm Deployer of SUSE Rancher Fleet 0.15 before 0.15.2, 0.14 before…
- CVE-2021-32024 — Critical (CVSS 9.8): A remote code execution vulnerability in the BMP image codec of BlackBerry QNX SDP version(s) 6.4 to 7.1 could allow an…
- CVE-2026-24307 — Critical (CVSS 9.3): Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information…
- CVE-2025-12977 — Critical (CVSS 9.1): Fluent Bit in_http, in_splunk, and in_elasticsearch input plugins fail to sanitize tag_key inputs. An attacker with…