CVE-2020-36319

LOWNVD 3.13.1—

3.1

Insecure configuration of default ObjectMapper in com.vaadin:flow-server versions 3.0.0 through 3.0.5 (Vaadin 15.0.0 through 15.0.4) may expose sensitive data if the application also uses e.g. @RestController

CVSS v3: 3.1
EG Score: 3.1(medium)
EPSS: 60.3%
KEV: Not listed

Published

April 23, 2021

Last Modified

November 21, 2024

References (6)

security@vaadinhttps://github.com/vaadin/flow/pull/8016
security@vaadinhttps://github.com/vaadin/flow/pull/8051
security@vaadinhttps://vaadin.com/security/cve-2020-36319
af854a3a-2127-422b-91ae-364da2661108https://github.com/vaadin/flow/pull/8016
af854a3a-2127-422b-91ae-364da2661108https://github.com/vaadin/flow/pull/8051
af854a3a-2127-422b-91ae-364da2661108https://vaadin.com/security/cve-2020-36319

Affected Packages

(1 across 1 ecosystem)

Maven(1)

Package	Vulnerable range	Fixed in	Dependents
com.vaadin:flow-server	3.0.0 ... 3.0.5 (6 versions)	3.0.6	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 17:32 UTCEG score recompute
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2020-36319?

CVE-2020-36319 is a low vulnerability published on April 23, 2021. Insecure configuration of default ObjectMapper in com.vaadin:flow-server versions 3.0.0 through 3.0.5 (Vaadin 15.0.0 through 15.0.4) may expose sensitive data if the application also uses e.g. @RestController

When was CVE-2020-36319 disclosed?

CVE-2020-36319 was first published in the National Vulnerability Database on April 23, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-36319 actively exploited?

CVE-2020-36319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-36319?

CVE-2020-36319 has a CVSS v3 base score of 3.1 (NVD).

How do I remediate CVE-2020-36319?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36319, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36319

Explore →

Is Your Infrastructure Affected by CVE-2020-36319?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-36319

📅 Published

🔄 Last Modified

🔗 References (6)

Affected Packages

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-36319?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)