How severe is CVE-2024-5217?

CVE-2024-5217 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2024-5217?

Affected package information for CVE-2024-5217 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2024-5217?

No patch has shipped for CVE-2024-5217 yet — track the servicenow servicenow advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2024-5217 across my infrastructure?

Inventory every servicenow servicenow deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2024-5217 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2024-5217?

O3 detects and blocks CVE-2024-5217 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2024-5217 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-5217, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-5217?

CVE-2024-5217 has an EPSS (Exploit Prediction Scoring System) score of 99.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2024-5217 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-5217 (ServiceNow Incomplete List of Disallowed Inputs Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-07-29. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-08-19. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-5217?

CVE-2024-5217 is classified as CWE-184 (CWE-184), CWE-697 (CWE-697). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-5217?

CVE-2024-5217 affects servicenow servicenow (3 versions, e.g. utah, vancouver, washington_dc). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2024-5217?

A Nuclei detection template exists for CVE-2024-5217, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-5217 published, and has it been updated?

CVE-2024-5217 was published on July 10, 2024 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-5217: Servicenow CWE-184 (Critical 9.8)

EPSS Exploitation Probability

via FIRST.org ↗

99.6%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

1 product · 99 configurations

Application

servicenowservicenow

3 versions

utahvancouverwashington_dc

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every servicenow servicenow deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2024-5217 yet — track the servicenow servicenow advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2024-5217 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2024-5217. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2024-5217 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2024-5217 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2024-5217

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2024-5217 being exploited in your environment?