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
Gmail Address Variants Bypass String Comparison and Enable Multiple Registrations
A single user created four separate accounts using valid Gmail address formats that all deliver to the same inbox: Ivan.Petrov@gmail.com, ivanpetrov@gmail.com, ivan.petrov+shop@gmail.com, and IVAN.PETROV@gmail.com. Simple string comparison in the registration code treated these as distinct entries, allowing circumvention of new-user promotions, free-tier limits, and one-application-per-person rules. The root cause lies in three Gmail-specific behaviors: case-insensitive local parts, plus-addressing that ignores everything after the + symbol, and dots that carry no semantic meaning in the local part. Additional risks arise from IDNA homograph domains that visually mimic legitimate addresses but encode to different Punycode strings. Proper mitigation requires storing both the original email for delivery and a domain-aware normalized form for uniqueness checks, combined with explicit IDNA validation on registration.
Dangling DNS Records Expose Companies to Subdomain Takeovers Years After Projects Shut Down
A marketing team requested reactivation of a three-year-old promotional landing page, only to discover that its domain now served an unrelated third-party website. The root cause was a forgotten CNAME record in the company's DNS zone that continued pointing to a project name on external hosting after the original service had been decommissioned. Because many hosting providers use wildcard DNS entries, standard availability checks and simple DNS resolution tests fail to detect that the target project no longer exists. Attackers who re-register the freed project name can then serve content under the company's legitimate subdomain, automatically obtaining valid TLS certificates and inheriting domain-wide cookies. The article details how such dangling records accumulate across infrastructure, marketing, and acquired company zones, and explains the concrete risks including cookie theft, bypass of Content-Security-Policy, and unauthorized domain ownership proofs. It concludes with a practical remediation workflow: export the full zone, assign owners to every record, validate external targets by application response rather than DNS resolution, and embed record removal into decommissioning procedures.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript engine that is being actively exploited in the wild. The flaw is a type confusion issue within the Maglev compiler, specifically tied to optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Attackers can exploit the vulnerability by tricking victims into visiting a specially crafted HTML page, enabling remote code execution within the browser sandbox. The update brings Chrome to version 152.0.7977.82 or higher on Windows, macOS, and Linux, while also addressing a total of 12 vulnerabilities. The issue was reported by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Edge, Brave, Opera, and Vivaldi will require corresponding updates from their vendors.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript and WebAssembly engine that is being actively exploited in the wild. The flaw is a type confusion issue tied to the Maglev compiler and optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Successful exploitation allows a remote attacker to execute arbitrary code within the browser sandbox after a victim visits a specially crafted HTML page, a technique commonly seen in malvertising and compromised-site campaigns. The fix is included in Chrome 152.0.7977.82 and later for Windows, macOS, and Linux, and the update also resolves a total of twelve vulnerabilities. The vulnerability was reported on 4 August 2026 by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi will require corresponding updates from their respective vendors.