How severe is CVE-2016-5019?

CVE-2016-5019 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-5019?

CVE-2016-5019 affects the following packages: org.apache.myfaces.trinidad:trinidad (Maven), org.apache.myfaces.trinidad:trinidad (Maven), org.apache.myfaces.trinidad:trinidad (Maven), org.apache.myfaces.trinidad:trinidad (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-5019?

A fix is available for CVE-2016-5019; check the affected-versions list above or the advisory for the patched release of org.apache.myfaces.trinidad:trinidad, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2016-5019 in my Maven dependencies?

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

How do I mitigate CVE-2016-5019 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2016-5019 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-5019 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2016-5019?

CVE-2016-5019 has an EPSS (Exploit Prediction Scoring System) score of 8.0%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2016-5019?

CVE-2016-5019 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2016-5019 published, and has it been updated?

CVE-2016-5019 was published on October 3, 2016 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2016-5019 — trinidad

CRITICAL

CVE-2016-5019 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.myfaces.trinidad:trinidad. A fix is available for org.apache.myfaces.trinidad:trinidad — see the affected versions and patch details below.

Apache MyFaces Trinidad Deserialization Vulnerability

Also known asGHSA-x7rc-4gqw-3q6q

Published

Oct 3, 2016

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.apache.myfaces.trinidad:trinidad☕org.apache.myfaces.trinidad:trinidad☕org.apache.myfaces.trinidad:trinidad☕org.apache.myfaces.trinidad:trinidad

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

CoreResponseStateManager in Apache MyFaces Trinidad 1.0.0 through 1.0.13, 1.2.x before 1.2.15, 2.0.x before 2.0.2, and 2.1.x before 2.1.2 might allow attackers to conduct deserialization attacks via a crafted serialized view state string.

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.myfaces.trinidad:trinidad`	≥ 1.0.0	No fix
☕Maven	`org.apache.myfaces.trinidad:trinidad`	≥ 1.2.0&&< 1.2.15	1.2.15`org.apache.myfaces.trinidad:trinidad:1.2.15`
☕Maven	`org.apache.myfaces.trinidad:trinidad`	≥ 2.0.0&&< 2.0.2	2.0.2`org.apache.myfaces.trinidad:trinidad:2.0.2`
☕Maven	`org.apache.myfaces.trinidad:trinidad`	≥ 2.1.0&&< 2.1.2	2.1.2`org.apache.myfaces.trinidad:trinidad:2.1.2`

Affected Products

1 product · 4 configurations

Application

myfaces trinidadapache

≥ 2.1.0 && < 2.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.myfaces.trinidad:trinidad, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2016-5019; check the affected-versions list above or the advisory for the patched release of org.apache.myfaces.trinidad:trinidad, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-5019 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works