Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2021-29441: Authentication Bypass in Alibaba Nacos AuthFilter

Published Apr 27, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS83.2%100th percentile
CISA KEVNoNot listed
In the wildReported528 exploitation records in Mallory
Vendor
Alibaba Group
IdentifiersCVE-2021-29441CWE-290 · Authentication Bypass by Spoofing

CVE-2021-29441 is an authentication bypass vulnerability in Alibaba Nacos versions before 1.4.1. When built-in authentication is enabled, the AuthFilter servlet filter exempts requests identified as inter-server traffic using the client-controlled HTTP User-Agent header. An unauthenticated attacker can impersonate a Nacos server by setting this header to Nacos-Server, bypassing authentication checks and accessing administrative functionality.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Unauthenticated attackers can perform administrative operations on an affected Nacos instance, including accessing sensitive service configurations, modifying configuration data, and creating rogue administrator accounts. Exposed configurations can disclose cloud credentials, database passwords, API tokens, and private keys, enabling downstream compromise. Unauthorized configuration changes or deletion can disrupt dependent services. Remote code execution is not an intrinsic capability established for this vulnerability alone; it can arise through additional vulnerabilities or abuse of downstream services and exposed credentials.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to Nacos administrative and configuration interfaces to authorized clients and trusted cluster members using firewall rules, segmentation, or an authenticated access gateway. Remove unnecessary internet exposure and monitor for unexpected administrative account creation, bulk configuration retrieval, and unauthorized configuration changes. Do not treat the User-Agent header as proof of server identity.

Remediation

Patch, then assume compromise.

Upgrade affected Nacos installations to a currently supported release incorporating the fix introduced in version 1.4.1. Keep authentication enabled after upgrading; enabling authentication alone does not resolve the vulnerable header-based bypass. If exploitation is suspected, audit administrator accounts and configuration changes, remove unauthorized accounts, restore altered configurations from trusted backups, and revoke or rotate exposed credentials and cryptographic keys.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2021-29441This repository is a small standalone Python proof-of-concept/operational exploit for CVE-2021-29441, an authentication bypass in Alibaba Nacos before 1.4.1. The repo contains only two files: a README describing the vulnerability and exploit conditions, and a single executable script, exploit.py, which is the main entry point. The exploit works by creating a requests.Session and hardcoding the spoofed header 'User-Agent: Nacos-Server', which the vulnerable Nacos AuthFilter incorrectly trusts as an internal request marker. Using that bypass, the script interacts directly with Nacos administrative user-management APIs under /nacos/v1/auth/users. Capabilities implemented in code are broader than simple detection: it can check vulnerability by attempting to list users, enumerate existing users, create a new user with attacker-chosen credentials, delete an existing user, and update/reset a user's password. This makes it an operational exploit rather than a detection-only script. Repository structure is minimal and straightforward. README.md provides context, impact, affected versions, and remediation. exploit.py contains a NacosExploit class with helper request logic, individual methods for each administrative action, CLI argument parsing, and a main() routine. The script supports target selection, optional SSL verification disabling, and action flags (--check, --list, --create, --delete, --update-password). It prints status codes and optionally formats output with the rich library if installed. No reverse shell or post-exploitation implant is included; the payload is the crafted HTTP interaction itself. The primary security impact is unauthorized administrative access to Nacos user management over the network.K3ysTr0K3R · Disclosed Jun 25, 2026 · python · markdown · network · webOperationalvulhub-nacos-cve-2021-29441This 34-file repository is a deliberately vulnerable Nacos training environment with a standalone Python exploit, not an exploit-framework module. app/ contains the vendored Vulhub walkthroughs, upstream Compose configuration, requests dependency pin, and app/poc.py. The script accepts one target base URL, sends User-Agent: Nacos-Server to the user listing API, and conditionally submits an account-creation request for vulhub/vulhub. It checks response status and text but does not print the enumerated user data. It has no request timeouts or exception handling and exits with status 1 even after successful account creation. Detection alone does not distinguish a genuine bypass from an API already exposed because authentication is disabled. The documentation identifies versions before 1.4.1 as affected; the supplied target is specifically Nacos 1.4.0. build/nacos/Dockerfile enables authentication in vulhub/nacos:1.4.0 and clears JAVA_OPT to remove the upstream JDWP debugger. base/ preserves the upstream image Dockerfile. The separate vendored app/docker-compose.yml still exposes debugger port 5005 and uses the unmodified image, so it differs materially from the main lab configuration. Account creation is implemented, but administrator role assignment, full-console authorization, command execution, and flag retrieval are not demonstrated by the code. Although CTF metadata asks for a flag, no flag placement or retrieval implementation is present in the supplied files. isoloom.yml defines a single amd64 Nacos service on port 8848 within an offline lab network. .isoloom/ contains generated Docker Compose, Kubernetes manifests and check jobs, a multi-provider Vagrantfile, Proxmox Terraform, and six cloud Terraform variants for AWS, Azure, DigitalOcean, GCP, Linode, and OCI. Docker attempts to block internet access by removing the default route; Kubernetes expresses isolation through NetworkPolicies. checks/auth.sh verifies the server version and rejection of ordinary anonymous user listing, while generated checks test availability and isolation rather than the bypass itself. Cloud deployments restrict SSH and published Nacos access to an operator-supplied CIDR. GitHub workflows validate and run the lab and publish it through secret-configured services; their backend and token endpoint values are not supplied. Cleanup commands in provisioning and CI are contextual maintenance operations, not evidence of a fake exploit. The code-file count of 16 includes one Python file, five shell scripts, one Ruby Vagrantfile, seven Terraform files, and two Dockerfiles; YAML deployment/workflow files are recorded separately as declarative configuration. The original repository URL, analyzed git reference, and archive size were not provided, so their fields use empty-string/zero placeholders. UPSTREAM.md identifies the vendored Vulhub source commit as 8fd63916f7a8711e2e01dda0d27237e4d6175d38, not necessarily the commit of this repository. Analysis is static; no exploit or deployment was executed.CyberCTF · Disclosed Oct 8, 2026 · python · sh · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Alibaba GroupNacosapplication
FAQ

Frequently asked questions

Is CVE-2021-29441 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2021-29441?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2021-29441, the earliest disclosed Jun 25, 2026.
Is there a patch for CVE-2021-29441?
Upgrade affected Nacos installations to a currently supported release incorporating the fix introduced in version 1.4.1. Keep authentication enabled after upgrading; enabling authentication alone does not resolve the vulnerable header-based bypass.
What products are affected by CVE-2021-29441?
Alibaba Group Nacos.
How severe is CVE-2021-29441?
CVE-2021-29441 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 83.2% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence12Every report linking this CVE to a named adversary.
Associated malware29Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.