Advisory record · GHSA-8qv5-68g4-248j

Scala subject to file deletion, code execution due to Java deserialization chain with LazyList object deserialization

CVSS 9.8 CriticalCriticalEPSS 0.11 · 95th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.11 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 25 Sept 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.scala-lang:scala-libraryMaven>=2.13.0, <2.13.92.13.9
Identifiers
GHSA-8qv5-68g4-248j · CVE-2022-36944
Weakness (CWE)
CWE-502
Published
25 Sept 2022
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Scala library (org.scala-lang:scala-library) versions 2.13.0 up to but not including 2.13.9 contain a Java deserialization chain. It is only exploitable when an application deserializes LazyList objects, and an attacker who can supply serialized data to such an application could delete arbitrary files, make network connections, or possibly run arbitrary code. Upgrade to scala-library 2.13.9 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.11, the 95th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.