What is CVE-2024-4879?

CVE-2024-4879 is Jelly Template Injection Vulnerability in ServiceNow UI Macros. The supplied enrichment data classifies it as Unclassified mapped to CWE-1287 CWE-1287.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

39 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-4879 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Cyber Alliance (), Tick (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalpublic exploit

CVE-2024-4879

CVE-2024-4879 — Jelly Template Injection Vulnerability in ServiceNow UI Macros

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-4879 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jul 10, 2024Updated Jun 17, 2026Sources: NVD, ServiceNow (CNA), CISA, FIRST EPSS, GitHub, Exploit-DB, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jul 29, 2024

EPSS

100%

top of FIRST's scoreset

Affects

ServiceNow

11 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Now Platform to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Aug 19, 2024 — passed 760 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Status
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable
ServiceNow	Now Platform	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	servicenow.com (CNA), NVD, ServiceNow (CNA)
9.3	CVSS 4.0	critical	—	—	ServiceNow (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-1287 · Improper Validation of Specified Type of Input

Varies by Context::

Mitigation: Assume all input is malicious. Use an accept known good input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

Weakness & attack patterns

CWE-1287

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jul 29, 2024

Federal deadline

Aug 19, 2024

passed 760 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

🔒 Internet-facing ServiceNow without a verified patch is basically an open invitation. CVE-2024-4879 means “patch now, restrict access while checking”—not “add it to the backlog.” https://t.co/EKPYHjZsu0 #RemoteCodeExecution #CveVulnerabilities #VulnerabilityPatching https://t.co/W4uqo2RCv9
@windowsforum· Jul 20, 2026

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Now Platform.
Monitor for scanner or exploit-pattern traffic after 39 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Cyber AllianceTick

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
2025
Cve is exploited ServiceNow Multiple Versions - Input Validation & Template Injection
Aug 12, 2025 · SOCRadar CTI
Added · webapps entry: ServiceNow Multiple Versions - Input Validation & Template Injection
Aug 11, 2025 · Exploit-DB
2024
CVE is exploited. "fa-rrel/CVE-2024-4879"
Aug 27, 2024 · SOCRadar CTI
Added to CISA KEV catalog
Jul 29, 2024 · CISA
Initial · CVE published
Jul 10, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

15×TweetsAug 8, 2024 – Jul 21, 2026 · SOCRadar CTI
5×SVRS was changedAug 11, 2024 – Aug 15, 2024 · SOCRadar CTI
4×CVE modified by MITRE: CVSS metrics updated.Oct 21, 2025 – Nov 3, 2025 · SOCRadar CTI
3×Github ReposAug 14, 2024 – Sep 13, 2024 · SOCRadar CTI

References

8 on the record

support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644293
Permissions Required
support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1645154
Vendor Advisory
www.darkreading.com/cloud-security/patchnow-servicenow-critical-rce-bugs-active-exploit
Press/Media Coverage, Third Party Advisory, NIST, GITHUB
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-4879
US Government Resource
www.exploit-db.com/exploits/52410
Vendor Advisory
support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644293
NIST
support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1645154
NIST
nvd.nist.gov/vuln/detail/CVE-2024-4879
Vendor Advisory

Coverage

2 stories from the feeds we poll

Elsewhere on this site

ServiceNowevery CVE for this vendor
July 2024what else CISA listed
Unclassifiedsame class
CWE-1287other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-4879 is Jelly Template Injection Vulnerability in ServiceNow UI Macros, a critical vulnerability affecting Now Platform from ServiceNow. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 39 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.