Skip to main content
CVE-2022-36944VulnerabilityPublished Updated

CVE-2022-36944: n/a

Source CVE Database V5

0

Not known to be exploited · 10% EPSS · CVSS 9.8 Critical : upgrade to 2.13.9 as a priority.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2022

  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

Upgrade org.scala-lang/scala-library to 2.13.9.

Affected software

ProductAffectedFixed in
Mavenorg.scala-lang/scala-librarypkg:maven/org.scala-lang/scala-libraryOther threatsAffected
  • <2.13.9
Fixed in
  • 2.13.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading all Scala 2.13.x environments to version 2.13.9 or later where this vulnerability is addressed. In parallel, organizations must audit their applications for unsafe Java deserialization practices, especially where untrusted input is deserialized. Implementing strict input validation, employing allowlists for deserialization classes, and using serialization frameworks that enforce type safety can reduce risk. Application-layer mitigations such as enabling Java Security Manager policies to restrict file system and network access for deserialization processes can limit exploitation impact. Network segmentation and firewall rules should be enforced to restrict unnecessary outbound connections from application servers. Monitoring and logging deserialization activities and anomalous file operations can help detect exploitation attempts early. Finally, organizations should conduct threat modeling and penetration testing focused on deserialization attack vectors to identify and remediate vulnerabilities proactively.

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.

References

Community reviews

Loading reviews…