CVE-2022-36944 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.scala-lang:scala-library. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.scala-lang:scala-library — see the affected versions and patch details below.
Scala subject to file deletion, code execution due to Java deserialization chain with LazyList object deserialization
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36944.
EPSS Exploitation Probability
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
org.scala-lang:scala-libraryReal-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
Scala 2.13.x before 2.13.9 has a Java deserialization chain in its JAR file. On its own, it cannot be exploited. There is only a risk in conjunction with Java object deserialization within an application. In such situations, it allows attackers to erase contents of arbitrary files, make network connections, or possibly run arbitrary code (specifically, Function0 functions) via a gadget chain.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.scala-lang:scala-library | ≥ 2.13.0&&< 2.13.9 | 2.13.9org.scala-lang:scala-library:2.13.9 |
Affected Products
fedorafedoraprojectscalascala-langscala-collection-compatscala-langResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.scala-lang:scala-library, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.scala-lang:scala-library to 2.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36944 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Users of Scala's LazyList should never permit deserialization of untrusted data.Source: Red Hat security advisory for CVE-2022-36944 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Streams 2.4.0 | scala | RHSA-2023:3223 |
| Red Hat AMQ Streams 2.5.0 | see advisory | RHSA-2023:5165 |
Frequently Asked Questions
Is CVE-2022-36944 in your dependencies?
Find it across Maven, including transitive dependencies.