Skip to content
Fencer Vulns
critical 9.8

CVE-2020-17531 json

Deserialization flaw in EOL Tapestry 4.

published 2020-12-08 5 y ago modified 2026-06-17 4 mo ago also GHSA-c566-2grg-mjwg , EUVD-2022-0951

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.0%
EPSS 10.0% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

A Java Serialization vulnerability was found in Apache Tapestry 4. Apache Tapestry 4 will attempt to deserialize the "sp" parameter even before invoking the page's validate method, leading to deserialization without authentication. Apache Tapestry 4 reached end of life in 2008 and no update to address this issue will be released. Apache Tapestry 5 versions are not vulnerable to this issue. Users of Apache Tapestry 4 should upgrade to the latest Apache Tapestry 5 version.

Patch / fix

  • maven org.apache.tapestry:tapestry-project 5.0.1
  • apache tapestry 5.0.1

Exploit prediction

10.00% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.tapestry:tapestry-project
>=4.0, <5.0.1
5.0.1

Affected products

  • Apache Software Foundation Apache Tapestry

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.