Skip to content

Scala bug bounty programs

scala-lang.org Updated

Scala runs one public program: a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
1
1 pays cash
Targets in scope
11
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program Scala runs.

Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

11 targets. 6 excluded.

  • https://www.scala-lang.org

    Web

  • scala.util.matching and the regular-expression surface, plus the parser combinators and any other text-processing code the distribution ships

    Products and areas

  • Serialisation of Scala objects, including the interaction between Scala's collection and function classes and Java deserialisation

    Products and areas

  • The compiler across the supported lines: parsing, typechecking, implicit resolution, macro expansion and the bytecode the back end emits

    Products and areas

  • The compiler plugin interface and anything a plugin can do to emitted bytecode

    Products and areas

  • The compiler's handling of untrusted source, which matters directly for anything that compiles user-submitted code

    Products and areas

  • The macro system and compile-time execution, since compiling a project runs code that project supplied

    Products and areas

  • The published security process asks for vulnerabilities by email to the project's security address and sets a two-business-day acknowledgement target. It declares no narrower scope, so the compiler, the standard library and the release tooling are all in

    Products and areas

  • The release and publication path: signing, the PGP keys the project publishes and the artifacts pushed to Maven Central

    Products and areas

  • The REPL and the scripting entry points, which evaluate source straight from input

    Products and areas

  • The standard library: collections, scala.io, scala.sys.process, string handling and the implicit machinery that decides what code runs

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 6

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Apache Spark, Kafka, Akka, Pekko, Flink and Play, all separate projects with their own security processes

  • Compiling source the developer wrote and trusted, since running a build is what the compiler is for

  • sbt, Mill and other build tools, which are separate projects

  • Scala application code with a bug of its own, as distinct from a compiler or standard library defect

  • The JVM itself and the JDK class library underneath Scala

  • Third-party Scala libraries published to Maven Central by other authors

Recent changes

Reward and scope changes across every Scala program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in Scala products, from the NVD.

Search NVD
  • CVE-2022-36944 Critical

    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.

  • The compilation daemon in Scala before 2.10.7, 2.11.x before 2.11.12, and 2.12.x before 2.12.4 uses weak permissions for private files in /tmp/scala-devel/${USER:shared}/scalac-compile-server-port, which allows local users to write to arbitrary class files and consequently gain privileges.

About this page

This page gathers every public program listed under scala-lang.org: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.