Is com.alibaba:fastjson 1.1 vulnerable?
Maven · 61 releases from 1.1.15 to 1.1.77 · latest com.alibaba:fastjson is 2.0.66 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. com.alibaba:fastjson 1.1.77, the last 1.1 release, is affected by 2 known security advisories (2 critical), including CVE-2025-70974, CVE-2017-18349. Upgrade to 1.2.48 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=com.alibaba:fastjson -DdepVersion=1.2.48 -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
Advisories affecting com.alibaba:fastjson 1.1.77
FASTJSON Includes Functionality from Untrusted Control Sphere
- Affected
- <1.2.48
- Fixed in
- 1.2.48
Improper Input Validation in alilibaba:fastjson
- Affected
- <1.2.31
- Fixed in
- 1.2.31
Every com.alibaba:fastjson 1.1.x release
Affected: 1.1.16 to 1.1.77. Latest com.alibaba:fastjson: 2.0.66.
| Version | Known advisories |
|---|---|
| com.alibaba:fastjson 1.1.77 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.76 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.73 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.72 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.71 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.70 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.69 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.68 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.67 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.66 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.65 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.64 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.63 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.62 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.61 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.60 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.59 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.58 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.57 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.56 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.55 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.54 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.53 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.52 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.51 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.50 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.49 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.48 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.47 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.46 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.45 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.44 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.43 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.42 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.41 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.40 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.39 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.38 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.37 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.36 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.35 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.34 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.33 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.32 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.31 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.30 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.29 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.28 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.27 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.26 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.25 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.24 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.23 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.22 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.21 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.20 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.19 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.18 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.17 | CVE-2025-70974, CVE-2017-18349 |
| com.alibaba:fastjson 1.1.16 | CVE-2025-70974, CVE-2017-18349 |
Which of your client projects are still on com.alibaba:fastjson 1.1?
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.