Out-of-bounds Write in Play Framework

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2020-27196: 1.40% estimated exploitation activity in the next 30 days; percentile 72.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An issue was discovered in PlayJava in Play Framework 2.6.0 through 2.8.2. The body parsing of HTTP requests eagerly parses a payload given a Content-Type header. A deep JSON structure sent to a valid POST endpoint (that may or may not expect JSON payloads) causes a StackOverflowError and Denial of Service.

Published by the source

10 Feb 2022, 20:23 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h48w-c35p-6m8x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-27196

Advisory: Out-of-bounds Write in Play Framework
IDs: CVE-2020-27196, GHSA-h48w-c35p-6m8x
Record: https://patchnext.com/advisories/cve-2020-27196 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.typesafe.play:play 2.8.3, 2.7.6; com.typesafe.play:play-java 2.8.3, 2.7.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.typesafe.play:play: affected >= 2.6.0, < 2.7.6; >= 2.8.0, < 2.8.3; fixed in 2.7.6, 2.8.3
- Maven com.typesafe.play:play-java: affected >= 2.6.0, < 2.7.6; >= 2.8.0, < 2.8.3; fixed in 2.7.6, 2.8.3

## Suggested inspection (read-only)
- Maven com.typesafe.play:play: check the installed version with your package manager.
- Maven com.typesafe.play:play-java: 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 com.typesafe.play:play, com.typesafe.play:play-java.
- 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-h48w-c35p-6m8x (GitHub-reviewed advisory GHSA-h48w-c35p-6m8x lists affected ranges: Maven com.typesafe.play:play >=2.6.0 =2.8.0 =2.6.0 =2.8.0 <2.8.3)

Commands are suggestions: review each one before running it.