Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2020-27196 — play

HIGHFix: playframework/playframework#10321

CVE-2020-27196 is a high-severity (CVSS 7.5) Out-of-bounds Write vulnerability in com.typesafe.play:play. A fix is available for com.typesafe.play:play — see the affected versions and patch details below.

Out-of-bounds Write in Play Framework

Also known asGHSA-h48w-c35p-6m8x
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.03%0.65%1.28%1.90%0.5%1.4%Apr 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-27196 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected
☕com.typesafe.play:play☕com.typesafe.play:play☕com.typesafe.play:play-java☕com.typesafe.play:play-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.typesafe.play:play≥ 2.6.0&&< 2.7.62.7.6com.typesafe.play:play:2.7.6
☕Mavencom.typesafe.play:play≥ 2.8.0&&< 2.8.32.8.3com.typesafe.play:play:2.8.3
☕Mavencom.typesafe.play:play-java≥ 2.6.0&&< 2.7.62.7.6com.typesafe.play:play-java:2.7.6
☕Mavencom.typesafe.play:play-java≥ 2.8.0&&< 2.8.32.8.3com.typesafe.play:play-java:2.8.3

Affected Products

1 product · 3 configurations
Application
play frameworklightbend
≥ 2.8.0 && ≤ 2.8.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.typesafe.play:play, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.typesafe.play:play to 2.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-27196 is resolved across your whole dependency graph.

  3. Workarounds

    Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2020-27196 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-27196: play DoS — Fixed in 2.7.6