
Zero-dependency, offline CLI scanner that finds fastjson inside JARs and Spring Boot fat-JARs, flags CVE-2026-16723 exposure, and detects shaded dependencies for CI gating.
One command to find out whether your Java application contains fastjson, where it is hidden, and whether it is affected by CVE-2026-16723.
Zero dependencies · Fully offline · A single 23KB jar · Supports Java 8+
On July 21, 2026, the fastjson maintainers disclosed CVE-2026-16723 (CVSS 9.0, remote code execution):
A large number of security advisories (including several English-language security media outlets) still claim that "1.x is EOL, there will never be a patch, and the only option is to migrate to fastjson2." That claim has been false since 2026-07-29. You can verify it yourself:
| Evidence | Link |
|---|---|
Maven Central hosts com.alibaba:fastjson:1.2.84, jar uploaded on 2026-07-29 | repo1 |
GitHub release 1.2.84, published at 2026-07-29T08:24:51Z | release |
Key commit fix: strengthen autoType type name validation and whitelist verification | 2026-07-29T07:02:55Z |
1.2.83 was released in May 2022, and the 1.x branch had no commits for four years afterward — 1.2.84 was released as a special exception specifically for this vulnerability.
Its release title does not mention a security fix: the title of 1.2.83 says "(security fix)", while 1.2.84 only says
"1.2.84版本发布" (1.2.84 version released). But the body does mention it — there is a complete Security Fixes section listing four AutoType
hardening items one by one, and it has been that way since the day of release (2026-07-29) (verifiable via the Wayback archive 20260729094935).
As for why most security advisories and scanners still have not caught up after the patch was released, I have not figured it out, and I will not speculate here.
📌 Correction on 2026-08-14: this originally said "the full text does not mention security, so it was not followed up." The first half has been empirically proven wrong based on the release body and the same-day Wayback archive (only the title lacks the label), so the second half loses its basis as well and has been removed.
👉 Practical impact for 1.x users: upgrading to 1.2.84 is the lowest-cost remediation (a minor version in the same branch, usually requiring no code changes), so you are not forced to immediately undertake a major-version migration to fastjson2. This tool gives recommendations accordingly.
⚠️ The prerequisite is JDK 8 or above (tested on 2026-10-14): all 274 classes in 1.2.84 are Java 8 bytecode (major 52), while 1.2.83 is Java 5 (major 49). On JDK 7 (Zulu 7u352),
javaconly gives a warning with exit code 0, but at runtime it directly throwsUnsupportedClassVersionError: com/alibaba/fastjson/JSON : Unsupported major.minor version 52.0. Also: theJSON.VERSIONconstant in 1.2.84 is still"1.2.83", so judging the version by it will be wrong; this tool readspom.propertiesinstead and is unaffected.
And the most troublesome part is:
fastjson is usually a transitive dependency — nobody installs it on purpose; it is pulled in by another library. Many teams have no idea they are using it.
mvn dependency:tree can list dependencies, but it is powerless in two situations:
This tool was written for these two situations.
Download fastjson-check.jar from Releases, then:
# 扫一个 jar(Spring Boot fat-JAR 会自动逐层展开)
java -jar fastjson-check.jar ./myapp.jar
# 扫一整个目录(递归查找所有 jar/war)
java -jar fastjson-check.jar /opt/apps
# 输出 JSON,接入流水线
java -jar fastjson-check.jar /opt/apps --json
No installation, no account, no internet connection, no data upload.
The same artifact is both a CLI and a Maven plugin. This usage does not require downloading the jar first:
# 在你的项目目录下直接跑,扫的是 Maven 解析后的依赖
mvn io.github.xiaoqimikko:fastjson-check:0.3.1:check
Or bind it into the build lifecycle (the verify phase):
<plugin>
<groupId>io.github.xiaoqimikko</groupId>
<artifactId>fastjson-check</artifactId>
<version>0.3.1</version>
<executions>
<execution>
<goals><goal>check</goal></goals>
</execution>
</executions>
</plugin>
pom.xmlWhen the CLI scans pom.xml, it reads text, but in real projects fastjson's version is often not in that text:
<version>${fastjson.version}</version><parent>, so that line doesn't exist in your own pomThe plugin gets Maven's post-resolution dependency set, where each dependency carries the real jar path in the local repository.
So it takes exactly the path this tool is best at: scanning com/alibaba/fastjson(2)/JSON.class inside the real jar,
rather than trusting what the pom says.
⚠️ But the detection boundary hasn't changed because of this: the decision key is still that class path, so dependencies that have been relocated / repackaged under a different package name still can't be detected (see "What it isn't" below). The plugin solves "where the version is written", not "the package name was changed".
| Parameter | Default | Description |
|---|---|---|
-Dfastjson-check.failOnFound | false | Fail the build when CRITICAL / HIGH is found |
-Dfastjson-check.path | unset | Don't scan the dependency tree; scan this path instead (directory / jar / war / fat-jar) |
-Dfastjson-check.skip | false | Skip execution |
🔴 Not failing the build by default is intentional, and differs from the CLI's exit-code semantics:
the command line is something you type yourself, so exit code 1 is exactly what you want; but the plugin runs on the pipeline,
and a self-check tool shouldn't turn the build red when you're not expecting it. To use it as a CI gate, explicitly add
-Dfastjson-check.failOnFound=true.
💡 On Windows, if the report shows garbled characters, switch the console back to GBK (
chcp 936) — in plugin mode the output encoding is decided by Maven, and the CLI's--utf8/--gbkswitches can't reach it here.
fastjson-check 0.1.0 —— fastjson 应急排查(离线,不外传任何数据)
扫描目标:myapp.jar
已展开归档:3 个
发现 2 处 fastjson:
[CRITICAL] fastjson 1.2.83
位置 :myapp.jar!/BOOT-INF/lib/fastjson-1.2.83.jar
版本来源:pom.properties
场景 :Spring Boot fat-JAR ← CVE-2026-16723 的主要在野利用场景
结论 :命中 CVE-2026-16723(CVSS 9.0 远程代码执行),默认配置即可利用
处置 :1.x 已停止维护,不会有修复版本。应急处置二选一:①(推荐)迁移至
fastjson2 2.0.63 或更高版本;② 无法立即迁移时,先启用 SafeMode
彻底关闭 AutoType 以缓解,但这不是长期方案。