CVE-2021-29442
Published: April 11, 2026
Official Description
Nacos is a platform designed for dynamic service discovery and configuration and service management. In Nacos before version 1.4.1, the ConfigOpsController lets the user perform management operations like querying the database or even wiping it out. While the /data/remove endpoint is properly protected with the @Secured annotation, the /derby endpoint is not protected and can be openly accessed by unauthenticated users. These endpoints are only valid when using embedded storage (derby DB) so this issue should not affect those installations using external storage (e.g. mysql)
Risk Analysis
This Nacos vulnerability allows unauthenticated users to access the /derby endpoint in versions prior to 1.4.1 when using embedded storage. This enables management operations, including querying or wiping out the database. Its inclusion in CISA's KEV catalog makes it an urgent concern.
This vulnerability is actively exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog. It is remotely exploitable by accessing an unprotected endpoint.
Upgrade Nacos to version 1.4.1 or later. If using embedded storage, consider migrating to external storage like MySQL. Implement strict access controls to Nacos instances.
Technical Analysis
CVE-2021-29442 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2021-29442 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2021-29442 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1