CVE-2024-5217: Unauthenticated remote code execution in ServiceNow GlideExpression
- Vendor
- Servicenow
CVE-2024-5217 is an input-validation vulnerability affecting ServiceNow Now Platform Washington DC, Vancouver, and earlier releases, including Utah. Incomplete filtering of disallowed inputs in GlideExpression script processing can allow an unauthenticated remote attacker to execute code in the context of the Now Platform. Technical accounts describe a GlideExpressionScript namespace-validation bypass involving single-quoted declarations. Some accounts instead assign a filesystem blacklist bypass to this CVE, creating uncertainty over the attribution of individual components in the associated three-vulnerability exploit chain.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise a ServiceNow instance through unauthenticated code execution and expose its stored data. Exploitation has been associated with data-theft attacks. When chained with CVE-2024-4879 and CVE-2024-5178, the vulnerabilities can provide full database access, sensitive file access, and command execution on configured MID Servers inside customer networks. These broader outcomes are documented for the combined chain and should not all be attributed to CVE-2024-5217 alone.
Mitigation
If you can’t patch tonight, do this now.
Restrict network and application access to affected instances while patches are pending. Increase access-log monitoring and detection, configure suspicious-login alerts, and promptly investigate unusual activity. These controls reduce exposure or improve detection but are not a substitute for installing the applicable security fixes.
Remediation
Patch, then assume compromise.
Apply the vendor security patch or hotfix specifically addressing CVE-2024-5217 for the installed release. Listed fixed levels are Utah Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1; Vancouver Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10; and Washington DC Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, Patch 4, or Patch 5. Confirm applicability against the vendor's CVE-specific guidance and verify that hosted instances received the update. Customer patches were applied during June 2024, with security updates also announced in July. Patching prevents future exploitation but does not remove an existing compromise; investigate suspected historical exploitation separately.
Exploits
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2024-5217 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 29, 2024.
- Is there a public exploit for CVE-2024-5217?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-5217.
- Is there a patch for CVE-2024-5217?
- Apply the vendor security patch or hotfix specifically addressing CVE-2024-5217 for the installed release. Listed fixed levels are Utah Patch 10 Hot Fix 3, Patch 10a Hot Fix 2, or Patch 10b Hot Fix 1; Vancouver Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9 Hot Fix 1, or Patch 10; and Washington DC Patch 1 Hot Fix 3b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 2, Patch 4, or Patch 5.
- What products are affected by CVE-2024-5217?
- Servicenow.
- How severe is CVE-2024-5217?
- CVE-2024-5217 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 99.6% (100th percentile) as of Oct 16, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.