Skip to content
Reachability Analysis

CVE-2026-16723: Alibaba fastjson 1.x, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: noWalk it through the four questions

What the flaw is

fastjson is a widely used Java JSON library. CVE-2026-16723 is a remote code execution flaw (CWE-502, deserialization of untrusted data) in the 1.x line. It can be triggered under the stock default configuration: AutoType is off and SafeMode is off, and no AutoType enablement or classpath gadget is needed. Per the 1.2.84 notes, a type name that contains URL-special characters could reach resource probing and the class loader, and the fix rejects such names before that point.

The advisory names one deployment prerequisite: the application runs as a Spring Boot executable fat-jar (started with java -jar). It says the flaw is reachable through JSON.parse, JSON.parseObject(String) and JSON.parseObject(String, Class). Naming a target class is not a mitigation, because an attacker can nest the payload inside an Object or Map field of that class. An attacker who can send JSON to such a parse call can run code in the application.

The advisory is dated 21 Jul 2026, the disclosure date; NVD published the record on 23 Jul 2026. The CNA rates it 9.0 (CVSS 3.1 base score): network, high attack complexity, no privileges, scope changed. NVD lists the record as Deferred and has added no CVSS score of its own.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the application ships fastjson 1.2.68 to 1.2.83 and is not a noneautotype buildMaven: mvn dependency:tree -Dincludes=com.alibaba:fastjson prints a line such as +- com.alibaba:fastjson:jar:1.2.83:compile for an affected build and +- com.alibaba:fastjson:jar:1.2.83_noneautotype:compile for a noneautotype build. Gradle: gradle dependencies --configuration runtimeClasspath | grep -i fastjson. On a built artifact: jar tf app.jar | grep -i fastjson (a fat-jar lists BOOT-INF/lib/fastjson-1.2.x.jar). Also check your SBOM. A noneautotype build has the vulnerable code removed; a plain 1.2.83 does not. The advisory states that 1.2.60 and earlier lack the code path and that 1.2.84 and all fastjson2 versions are not affected. It gives no status for 1.2.61 to 1.2.67, so treat those as unconfirmed and move to 1.2.84.
it runs as a Spring Boot executable fat-jar with SafeMode off and passes untrusted JSON to JSON.parse or JSON.parseObjectFat-jar: jar tf app.jar | grep -m1 BOOT-INF shows the Spring Boot nested layout (application classes in BOOT-INF/classes, dependencies in BOOT-INF/lib, per the Spring Boot executable jar documentation); on a running host ps -o args= -p PID shows java -jar app.jar. SafeMode off and AutoType off (both are the stock defaults): ps -ef | grep fastjson.parser.safeMode, unzip -p app.jar BOOT-INF/classes/fastjson.properties for fastjson.parser.safeMode=true, and grep -rn 'setSafeMode' src/. Untrusted parse: grep -rnE 'JSON\.parse(Object)?\(' src/ and trace each hit back to a request body, queue message, cache value or file an outsider can influence; naming a target class does not remove the exposure. A WAR in an external Tomcat or Jetty is outside the advisory's trigger condition.

Affected and fixed versions

Scroll the table sideways for more columns

The advisory was dated 21 Jul 2026 and updated on 29 Jul 2026. The fastjson 1.x repository was archived by its owner on 29 Jul 2026 and is read-only.
Product lineAffectedFirst fixed or not affectedNotes
fastjson 1.x (com.alibaba:fastjson)1.2.68 to 1.2.831.2.84 (released 29 Jul 2026)Versions 1.2.60 and earlier lack the vulnerable code path
fastjson 1.x 1.2.61 to 1.2.67Not stated in the advisory1.2.84The advisory lists 1.2.68 as the first affected version and 1.2.60 as the last version without the path; it is silent between them, so upgrade to 1.2.84
fastjson 1.x noneautotype buildsNot affectedNot applicableVulnerable code removed at compile time; example artifact version 1.2.83_noneautotype
fastjson2Not affected (all versions)Not applicableType resolution was designed without the resource probing step

If the fix cannot go in yet

  • Upgrade to com.alibaba:fastjson:1.2.84. This is the fix. Cost: the 1.2.84 release also tightens AutoType handling, so an application that relies on an accept list prefix to cover base types such as ClassLoader, DataSource or RowSet will stop accepting them; only a full type name entry is an opt-in.
  • Turn on SafeMode with -Dfastjson.parser.safeMode=true, or ParserConfig.getGlobalInstance().setSafeMode(true), or fastjson.parser.safeMode=true in fastjson.properties (advisory, P0 action). Cost: SafeMode disables AutoType completely, so any code that depends on @type polymorphic deserialization stops working.
  • Switch to a noneautotype build (Maven example 1.2.83_noneautotype). Cost: the AutoType code is gone, so @type deserialization no longer works.
  • Migrate to fastjson2, which Alibaba rates as removing the issue under its default configuration (advisory P1 action). Cost: a code migration; the project publishes an upgrade guide and a compatibility package.
  • Avoid fat-jar deployment: the advisory's not-affected table lists plain jar, uber-jar and WAR deployments as not meeting the trigger condition. Cost: a change to the packaging and the run command, with its own testing. Prefer the upgrade.

What to look for

  • Alibaba, NVD and CISA publish no indicators of compromise, log signatures or sample traffic for this CVE. The advisory's guidance is to find affected services and upgrade or enable SafeMode.
  • After finding the services, list the call sites that pass request data to JSON.parse or JSON.parseObject.
  • The 1.2.84 release notes say type names containing the characters : / or ! are now rejected before class loading. On a patched build, request bodies or WAF logs that carry an @type value with those characters therefore mark attempts to reach the flaw; Alibaba publishes no exception text for them.

No public report dates the start of exploitation.

Exploitation reported so far

CVE-2026-16723 is not in the CISA KEV catalog as of 18 Nov 2026, and the CISA coordinator SSVC entry on the NVD record, stamped 23 Jul 2026, rates exploitation as none. No use in the wild is published.

Alibaba's advisory says the finder verified the flaw end to end on Spring Boot 2.x, 3.x and 4.x with JDK 8, 11, 17 and 21. The advisory and NVD cite no public proof of concept.

Why static reachability settles it

Every condition here is a fact in the build or the code: the fastjson version, fat-jar packaging, the SafeMode setting and a call path from untrusted input to the parser. Static reachability checks those without waiting for traffic. No one reports attacks yet, so a CVSS score alone would over- or under-state the risk for any one service. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-16723: NVD record, read 19 Nov 2026
  2. CVE-2026-16723: vendor advisory (fastjson2 wiki, dated 21 Jul 2026, updated 29 Jul 2026), read 19 Nov 2026
  3. CVE-2026-16723: vendor release notes for fastjson 1.2.84, read 19 Nov 2026
  4. CVE-2026-16723: vendor SafeMode documentation, read 19 Nov 2026
  5. CVE-2026-16723: Spring Boot executable jar documentation, read 19 Nov 2026
  6. CVE-2026-16723: CISA KEV feed (version 2026.11.18, no entry for this CVE), read 19 Nov 2026

Last reviewed 19 Nov 2026.