sbt vulnerable to arbitrary file write via archive extraction (Zip Slip)
CVE-2023-46122GHSA-h9mw-grgx-2fhf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.scala-sbt:sbt 1.9.7; org.scala-sbt:io_3 1.9.7; org.scala-sbt:io_2.13 1.9.7; org.scala-sbt:io_2.12 1.9.7), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.scala-sbt:sbt
- Affected
- >= 0.3.4, < 1.9.7
- Fixed in
- 1.9.7
Maven org.scala-sbt:io_3
- Affected
- >= 1.0.0, < 1.9.7
- Fixed in
- 1.9.7
Maven org.scala-sbt:io_2.13
- Affected
- >= 1.0.0, < 1.9.7
- Fixed in
- 1.9.7
Maven org.scala-sbt:io_2.12
- Affected
- >= 1.0.0, < 1.9.7
- Fixed in
- 1.9.7
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h9mw-grgx-2fhf lists affected ranges: Maven org.scala-sbt:sbt >=0.3.4 =1.0.0 =1.0.0 =1.0.0 <1.9.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.9 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
- EPSS
- CVE-2023-46122: 0.37% estimated exploitation activity in the next 30 days; percentile 30.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Given specially crafted zip or JAR file, IO.unzip allows writing of arbitrary file. The follow is an example of a malicious entry: This would have a potential to overwrite /root/.ssh/authorizedkeys. Within sbt's main code, IO.unzip is used in pullRemoteCache task and Resolvers.remote; however many projects use IO.unzip(...) directly to implement custom tasks - https://github.com/search?q=IO.unzip+language%3AScala&type=code&l=Scala&p=1 Patches The problem has been patched in https://github.com/sbt/io/pull/360 sbt 1.9.7 is available with the fix. Workarounds A workaround might be use some other library to unzip. References - https://github.com/snyk/zip-slip-vulnerability - https://security.snyk.io/vuln/SNYK-JAVA-ORGCODEHAUSPLEXUS-31680 - https://github.com/sbt/io/issues/358
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-h9mw-grgx-2fhf
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-46122 Advisory: sbt vulnerable to arbitrary file write via archive extraction (Zip Slip) IDs: CVE-2023-46122, GHSA-h9mw-grgx-2fhf Record: https://patchnext.com/advisories/cve-2023-46122 (revision 1, source checked 26 Oct 2026, 16:17 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.scala-sbt:sbt 1.9.7; org.scala-sbt:io_3 1.9.7; org.scala-sbt:io_2.13 1.9.7; org.scala-sbt:io_2.12 1.9.7. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.scala-sbt:sbt: affected >= 0.3.4, < 1.9.7; fixed in 1.9.7 - Maven org.scala-sbt:io_3: affected >= 1.0.0, < 1.9.7; fixed in 1.9.7 - Maven org.scala-sbt:io_2.13: affected >= 1.0.0, < 1.9.7; fixed in 1.9.7 - Maven org.scala-sbt:io_2.12: affected >= 1.0.0, < 1.9.7; fixed in 1.9.7 ## Suggested inspection (read-only) - Maven org.scala-sbt:sbt: check the installed version with your package manager. - Maven org.scala-sbt:io_3: check the installed version with your package manager. - Maven org.scala-sbt:io_2.13: check the installed version with your package manager. - Maven org.scala-sbt:io_2.12: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.scala-sbt:sbt, org.scala-sbt:io_3, org.scala-sbt:io_2.13, org.scala-sbt:io_2.12. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-h9mw-grgx-2fhf (GitHub-reviewed advisory GHSA-h9mw-grgx-2fhf lists affected ranges: Maven org.scala-sbt:sbt >=0.3.4 =1.0.0 =1.0.0 =1.0.0 <1.9.7) Commands are suggestions: review each one before running it.
Loading voting…