Deserialization of Untrusted Data in Jodd

published 2020-05-21 6y ago modified 2026-06-17 4mo ago also GHSA-jrg3-qq99-35g7 , EUVD-2022-1082

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

Jodd before 5.0.4 performs Deserialization of Untrusted JSON Data when setClassMetadataName is set.

Patch / fix

fixed in 2 links 1

maven org.jodd:jodd-json 5.0.4
jodd jodd 5.0.4

github.com/oblac/jodd@9bffc39 commit

Is CVE-2018-21234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

8.32% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

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.jodd:jodd-json	<5.0.4	5.0.4

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel 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.