Skip to main content
VulnerabilityPublished Updated

CVE-2024-22871: Clojure · Deserialization of Untrusted Data

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor official Clojure repositories and security advisories for patches or updates addressing CVE-2024-22871 and apply them promptly once available.
  2. Implement network-level access controls such as firewalls and intrusion prevention systems to restrict exposure of Clojure-based services to untrusted networks.
  3. Employ application-layer rate limiting and input validation to reduce the risk of triggering the vulnerable function with malicious payloads.
  4. Conduct code reviews and testing to identify usage of the clojure.core$partial$fn__5920 function and assess the potential for exploitation within your applications.
  5. Consider deploying runtime application self-protection (RASP) or behavior monitoring tools to detect abnormal application behavior indicative of DoS attempts.
  6. Prepare incident response plans to quickly isolate and remediate affected systems in case of exploitation.
  7. Where feasible, isolate vulnerable services in segmented network zones to limit the blast radius of potential attacks.
  8. Educate development and operations teams about the vulnerability and encourage secure coding practices to prevent similar issues.

Description

An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an attacker to cause a denial of service (DoS) via the clojure.core$partial$fn__5920 function.

References

Community reviews

Loading reviews…