Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Play 3.0.10

Latest

Choose a tag to compare

@github-actions github-actions released this 23 Dec 17:28
· 6 commits to refs/heads/3.0.x since this release
3.0.10
781cd7e

We are pleased to announce the release of Play 3.0.10! πŸŽ‰

πŸ“— About this Release

This release fixes several bugs and addresses reported security vulnerabilities (CVEs) and - as always - updates dependencies. We strongly recommend upgrading at your earliest convenience.

If you're considering upgrading to Play 3.0, please check the Play 3.0 release announcement for highlights and further details on how to migrate. Many projects have already smoothly upgraded to Play 3.0.

Noteworthy Pull Request

  • playframework/play-json#1228 [3.0.x] Avoid running out of memory when parsing heavily nested arrays or objects by @mkurz
    We now limit the maximum allowed nesting depth of JSON structures (arrays, objects, or a mix of both) to 1000.
    This limit can be adjusted using the system property play.json.parser.maxNestingDepth.
    We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
    This change helps prevent both potential OutOfMemoryErrors and StackOverflowErrors.
    The latter, however, is not a concern for Play JSON, since it already uses a @tailrec-optimized parsing method.
    As a result, Play JSON is not affected by GHSA-h46c-h94j-95f3, which specifically addresses StackOverflowError risks.
    This improvement is simply an additional safety measure.
  • #13684 [3.0.x] Bump to lz4-java 1.10.1 to fix CVE-2025-66566 and CVE‐2025‐12183 by @mkurz
  • #13706 [3.0.x] Netty 4.1.130.Final to fix CVE-2025-67735 by @mkurz
  • Upgrade ch.qos.logback:logback-core to fix CVE-2025-11226 (see "Patch updates" below)

Following pull requests got merged for this release:

For more details see the full list of changes and the 3.0.10 milestone.

❀️ Thanks to our premium sponsors!

If you find this OSS project useful for work, please consider asking your company to support it by becoming a sponsor.
You can also individually sponsor the project by becoming a backer.

πŸ™‡ Thanks to our contributors

Finally, thanks to the community for their help with detailed bug reports, discussions about new features and pull request reviews. This project is only possible due to the help we had from amazing contributors.
Special thanks to all code contributors who helped with this particular release (they are listed below)!