CVE-2024-5217

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-07-29), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 9.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

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

ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and earlier Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. The vulnerability is addressed in the listed patches and hot fixes below, which were released during the June 2024 patching cycle. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100CISA SSVC

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
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
100%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 10, 2024

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Oct 9, 2026
⚠️ Active exploitation confirmed. No fix on record yet. Sources: cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-5217
generic🔴 Active Exploitation

Patch Now: ServiceNow Critical RCE Bugs Under Active Exploit

https://www.darkreading.com/cloud-security/patchnow-servicenow-critical-rce-bugs-active-exploit
generic

CVE-2024-5217 – Incomplete Input Validation in GlideExpression Script - Security - Now Support Portal

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

Knowledge Article View - Now Support Portal

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 49× in last 7d / 217× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 944 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2024/CVE-2024-5217.yaml
    First seen Jan 1, 2024

    ServiceNow - Incomplete Input Validation

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2024-5217?
CVE-2024-5217 is a critical vulnerability published on July 10, 2024. ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and earlier Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. The vulnerability is addressed…
When was CVE-2024-5217 disclosed?
CVE-2024-5217 was first published on July 10, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-5217 actively exploited?
Yes. CISA added CVE-2024-5217 to the Known Exploited Vulnerabilities catalog on July 29, 2024, affecting ServiceNow Utah, Vancouver, and Washington DC Now Platform. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2024-5217?
CVE-2024-5217 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2024-5217?
CVE-2024-5217 affects ServiceNow Utah, Vancouver, and Washington DC Now Platform.
How do I remediate CVE-2024-5217?
No fix for CVE-2024-5217 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.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-5217

Explore →

Is Your Infrastructure Affected by CVE-2024-5217?

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

Book a Demo →Browse All CVEs