VYPR
High severityNVD Advisory· Published Nov 6, 2020· Updated Aug 4, 2024

CVE-2020-26883

CVE-2020-26883

Description

Play Framework 2.6.0 through 2.8.2 is vulnerable to stack consumption via unbounded recursion when parsing crafted JSON documents.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Play Framework 2.6.0 through 2.8.2 is vulnerable to stack consumption via unbounded recursion when parsing crafted JSON documents.

Vulnerability

CVE-2020-26883 is a denial-of-service vulnerability in Play Framework versions 2.6.0 through 2.8.2. The root cause is unbounded recursion during the parsing of specially crafted JSON documents, leading to excessive stack consumption [1].

Exploitation

Exploitation occurs remotely without authentication, as an attacker can send a malicious JSON payload as a form field to a Play application. The vulnerability specifically impacts applications using the PlayJava API flavor [3].

Impact

Successful exploitation causes uncontrolled recursion, exhausting the server's stack and resulting in a denial-of-service condition. No confidentiality or integrity impact is expected, but the availability impact is high [3].

Mitigation

Play Framework has fixed this issue in versions 2.8.3 and 2.7.6. Version 2.6.x is end-of-support and will not receive a patch; users should upgrade to a supported release immediately [2][3].

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
com.typesafe.play:playMaven
>= 2.6.0, < 2.7.62.7.6
com.typesafe.play:playMaven
>= 2.8.0, < 2.8.32.8.3
com.typesafe.play:play-javaMaven
>= 2.6.0, < 2.7.62.7.6
com.typesafe.play:play-javaMaven
>= 2.8.0, < 2.8.32.8.3

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.