Is com.alibaba:fastjson 1.2 vulnerable?
Maven · 81 releases from 1.2.0 to 1.2.84 · latest com.alibaba:fastjson is 2.0.66 · checked 18 Nov 2026
No known advisories in the last release
com.alibaba:fastjson 1.2.84, the last 1.2 release, has no known advisories. 4 advisories affect earlier 1.2.x releases, so update to 1.2.84.
mvn versions:use-dep-version -Dincludes=com.alibaba:fastjson -DdepVersion=1.2.84 -DforceVersion=trueIs your project on an affected com.alibaba:fastjson?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.2.x, affecting earlier releases
fastjson has a remote code execution (RCE) vulnerability
- Affected
- >=1.2.68 <=1.2.83
- Fixed in
- No fix released
FASTJSON Includes Functionality from Untrusted Control Sphere
- Affected
- <1.2.48
- Fixed in
- 1.2.48
Unsafe deserialization in com.alibaba:fastjson
- Affected
- >=1.2.25 <1.2.83
- Fixed in
- 1.2.83
Improper Input Validation in alilibaba:fastjson
- Affected
- <1.2.31
- Fixed in
- 1.2.31
Every com.alibaba:fastjson 1.2.x release
Affected: 1.2.21 to 1.2.83. 1.2.84 is not affected. Latest com.alibaba:fastjson: 2.0.66.
| Version | Known advisories |
|---|---|
| com.alibaba:fastjson 1.2.84 | None |
| com.alibaba:fastjson 1.2.83 | CVE-2026-16723 |
| com.alibaba:fastjson 1.2.80 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.79 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.78 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.77 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.76 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.75 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.74 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.73 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.72 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.71 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.70 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.69 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.68 | CVE-2026-16723, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.67 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.66 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.63 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.62 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.61 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.60 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.59 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.58 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.57 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.56 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.55 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.54 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.53 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.52 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.51 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.50 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.49 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.48 | CVE-2022-25845 |
| com.alibaba:fastjson 1.2.47 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.46 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.45 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.44 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.43 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.42 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.41 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.40 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.39 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.38 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.37 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.36 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.35 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.34 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.33 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.32 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.31 | CVE-2025-70974, CVE-2022-25845 |
| com.alibaba:fastjson 1.2.30 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.29 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.28 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.27 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.26 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.25 | CVE-2025-70974, CVE-2022-25845, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.24 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.23 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.22 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.2.21 | CVE-2025-70974, CVE-2017-18349 |
Which of your client projects are still on com.alibaba:fastjson 1.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.alibaba:fastjson version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other com.alibaba:fastjson versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.