Critical Fastjson Zero-Day CVE-2026-16723 Actively Exploited for Remote Code Execution on Java Servers

A critical zero-day vulnerability identified as CVE-2026-16723 is being actively exploited in Fastjson 1.x to achieve remote code execution on Java servers processing JSON data. The 1.x branch has no official patch, leaving mitigation options limited to enabling SafeMode, deploying a noneautotype build, or migrating to fastjson2.

The active exploitation of CVE-2026-16723 has placed significant pressure on security and development teams maintaining production Java services that rely on Fastjson 1.x. The flaw permits remote code execution without authentication, user interaction, or elevated privileges, making it especially dangerous for servers exposing JSON endpoints to the internet.

The issue affects Fastjson versions 1.2.68 through 1.2.83, including the final 1.2.83 release of the 1.x line. Exploitation works specifically when the application runs as a Spring Boot executable fat JAR launched with java -jar. Researchers have reproduced the attack on Spring Boot 2.x, 3.x, and 4.x across JDK 8, 11, 17, and 21.

The attack leverages deserialization and the @type mechanism. Even organizations that previously disabled AutoType remain vulnerable because the exploit functions under standard configurations with both AutoType and SafeMode turned off. The type resolution logic permits attacker-controlled resource lookups before restrictions are enforced.

Observed activity has focused primarily on organizations in the United States, with additional signals in Singapore and Canada. Impact spans financial services, healthcare, retail, and enterprise computing environments. A successful compromise can lead to full server control, credential theft, or deployment of additional malicious payloads.

Because no official update exists for Fastjson 1.x and a patch is considered unlikely, immediate mitigation requires enabling SafeMode via -Dfastjson.parser.safeMode=true, ParserConfig.getGlobalInstance().setSafeMode(true), or fastjson.properties. Where feasible, organizations should replace the dependency with com.alibaba:fastjson:1.2.83_noneautotype and plan migration to fastjson2, which uses a stricter allowlist design by default.