How severe is CVE-2024-22871?

CVE-2024-22871 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-22871?

CVE-2024-22871 affects the following packages: org.clojure:clojure (Maven), org.clojure:clojure (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-22871?

Update org.clojure:clojure to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22871 is resolved across your whole dependency graph.

How do I detect CVE-2024-22871 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.clojure:clojure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

No public exploit code has been indexed for CVE-2024-22871 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2024-22871 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-22871?

CVE-2024-22871 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2024-22871 was published on February 29, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2024-22871 — clojure

HIGH

CVE-2024-22871 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in org.clojure:clojure. A fix is available for org.clojure:clojure — see the affected versions and patch details below.

Reading specially crafted serializable objects from an untrusted source may cause an infinite loop and denial of service

Also known asGHSA-vr64-r9qj-h27f

Published

Feb 29, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-22871.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.clojure:clojure☕org.clojure:clojure

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Any program on the JVM may read serialized objects via java.io.ObjectInputStream.readObject(). Reading serialized objects from an untrusted source is inherently unsafe (this affects any program running on any version of the JVM) and is a prerequisite for this vulnerability.

Clojure classes that represent infinite seqs (Cycle, infinite Repeat, and Iterate) do not define hashCode() and use the parent ASeq.hashCode(), which walks the seq to compute the hash, yielding an infinite loop. Classes like java.util.HashMap call hashCode() on keys during deserialization of a serialized map.

The exploit requires:

Crafting a serialized HashMap object with an infinite seq object as a key.
Sending that to a program that reads serialized objects via ObjectInputStream.readObject().

This will cause the program to enter an infinite loop on the reading thread and thus a denial of service (DoS).

The affected Clojure classes (Cycle, Repeat, Iterate) exist in Clojure 1.7.0-1.11.1, 1.12.0-alpha1-1.12.0-alpha8.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.clojure:clojure`	≥ 1.7.0&&< 1.11.2	1.11.2`org.clojure:clojure:1.11.2`
☕Maven	`org.clojure:clojure`	≥ 1.12.0-alpha1&&< 1.12.0-alpha9	1.12.0-alpha9`org.clojure:clojure:1.12.0-alpha9`

Affected Products

2 products · 12 configurations

Application

clojureclojure

≥ 1.2.0 && < 1.11.2

1 version

1.12.0

fedorafedoraproject

3 versions

383940

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.clojure:clojure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.clojure:clojure to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22871 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

Any program on the JVM may read serialized objects via [java.io.ObjectInputStream.readObject()](https://docs.oracle.com/javase/8/docs/api/java/io/ObjectInputStream.html#readObject--). Reading serialized objects from an untrusted source is **inherently unsafe** (this affects any program running on any version of the JVM) and is a prerequisite for this vulnerability. Clojure classes that represent infinite seqs (Cycle, infinite Repeat, and Iterate) do not define hashCode() and use the parent ASeq.hashCode(), which walks the seq to compute the hash, yielding an infinite loop. Classes like java.u

O3 Security · Impact-Aware SCA

Is CVE-2024-22871 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works