Hispasec•July 28, 2026•🇪🇸Translated from Spanish

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.

Related articles

Habr•Vulnerabilities & Exploits

Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication

A detailed technical guide explains how to build asset scanning automation in MaxPatrol VM using its API, starting with authentication methods. The author covers three authorization options including local account login-password, domain account credentials, and reference tokens, providing working Python examples for local accounts. Code reads secrets from an .env file and obtains a Bearer token valid for 24 hours from the Core role instance. The post details required privileges in both the Management Console and MaxPatrol 10 for tasks such as vulnerability exports, dynamic asset group management, scan task creation, and report exporting. It credits Alexey Leonov for an early GitHub script that enabled practical API usage and lists additional resources including webinars, SDK, CLI, Jira integration, and a Postman collection. All subsequent API calls rely on the generated headers containing the Bearer token.

Habr•Vulnerabilities & Exploits

Securing Hadoop Clusters: Removing Passwords from XML Configs with Credential Provider API and JCEKS

Hadoop configurations frequently expose sensitive credentials such as database passwords and cloud access keys in plain text within files like hive-site.xml and core-site.xml. The Credential Provider API, introduced in Hadoop 2.6, allows applications to retrieve secrets from an external JCEKS keystore instead of embedding them directly in XML. This mechanism uses conf.getPassword() to fetch decrypted values from the keystore when hadoop.security.credential.provider.path is configured. JCEKS relies on the outdated PBEWithMD5AndTripleDES algorithm, which remains vulnerable to Sweet32 attacks in theory though practical risk for small keystore files is low. Master password protection for the keystore itself is the weakest link, with options including environment variables, protected password files, or HDFS Transparent Data Encryption. Arenadata has automated credential encryption management in its ADH platform through ADCM to handle keystore creation, permission setting, and rotation across cluster nodes.

Security NEXT•Vulnerabilities & Exploits

CISA Adds Five Exploited Vulnerabilities to KEV Catalog Including AhsayCBS Authentication and Command Injection Flaws

The US Cybersecurity and Infrastructure Security Agency (CISA) has added five vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. Four vulnerabilities were registered on October 14, 2026, and one additional entry followed on October 15. Among the newly listed issues are two critical flaws affecting the AhsayCBS backup management server: CVE-2026-105133, an authentication bypass in the API, and CVE-2026-105134, a command injection vulnerability in the replication feature. When chained together, the pair allows unauthenticated remote attackers to execute arbitrary operating system commands. Vendor Ahsay has released hotfixes in versions 10.3.4.45 and 9.15.2.70 because standard patches cannot fully address the issues. The advisory also references vulnerabilities in Atlassian products and multiple network security solutions from other vendors.

Security NEXT•Vulnerabilities & Exploits

Google Issues Chrome Security Update Fixing Critical Vulnerability Two Days After Previous Patch

Google has released a new set of security updates for its Chrome browser that address ten vulnerabilities, including one rated critical. The update arrives just two days after a larger patch that fixed 37 issues on October 13. The most severe flaw, tracked as CVE-2026-110922, is a use-after-free vulnerability in the Prerender feature that could allow remote code execution. The company released Chrome 155.0.8059.85 and 155.0.8059.84 for Windows and macOS, along with Chrome 155.0.8059.84 for Linux on October 15. The critical issue was reported by an external researcher on October 2. Deployment will occur gradually over the next several days to weeks.