Critical Nginx-ui MCP Flaw Actively Exploited in the Wild

A critical nginx-ui MCP flaw is being actively exploited, putting thousands of servers at risk. Tracked as CVE-2026-33032, this authentication bypass vulnerability carries a CVSS score of 9.8, making it one of the most severe threats currently facing system administrators. Discovered by Pluto Security, the flaw allows any network-adjacent attacker to take full control of an nginx server through a single unauthenticated API request.

Understanding the Nginx-ui MCP Flaw: Root Cause and Impact

So, what exactly went wrong? The vulnerability stems from a missing function call in the Model Context Protocol (MCP) implementation. Nginx-ui recently added MCP support, which splits communication across two HTTP endpoints. The /mcp endpoint properly includes both IP whitelisting and authentication middleware. However, the /mcp_message endpoint—which processes every tool invocation, including configuration writes and server restarts—shipped without any authentication check.

This omission exposes 12 MCP tools to unauthenticated callers. Seven of these are destructive, enabling attackers to inject nginx configurations, reload the server, and intercept all traffic passing through it. The remaining five provide reconnaissance capabilities, such as reading existing configs and mapping backend infrastructure. In other words, an attacker can silently take over your server and spy on your traffic.

Why This Nginx-ui MCP Flaw Demands Immediate Action

VulnCheck has already added the flaw to its Known Exploited Vulnerabilities (KEV) list. Meanwhile, Recorded Future’s Insikt Group independently flagged it in a recent report as one of 31 high-impact vulnerabilities exploited during March 2026, assigning it a risk score of 94 out of 100. These endorsements underscore the severity of the threat.

Pluto Security’s researchers used Shodan to identify over 2,600 publicly reachable nginx-ui instances across cloud providers including Alibaba Cloud, Oracle, and Tencent. Most were running on the default port 9000. The tool’s Docker image has been pulled more than 430,000 times, suggesting a much larger population of potentially vulnerable deployments sitting behind firewalls. Therefore, the actual number of at-risk instances could be significantly higher.

What Makes This Vulnerability Particularly Dangerous

This is the second MCP vulnerability Pluto Security has disclosed in recent weeks, following MCPwnfluence, an SSRF-to-RCE chain in the Atlassian MCP server. Both cases expose a recurring weakness: when MCP is connected to existing applications, its endpoints often inherit full capabilities without inheriting any of the security controls. As a result, a single missing check can compromise an entire system.

How to Protect Your Servers from the Nginx-ui MCP Flaw

The nginx-ui maintainers released a patch in version 2.3.4 just one day after disclosure. The fix amounted to 27 characters of added code, along with a regression test to prevent the same oversight from recurring. Organizations running nginx-ui with MCP enabled should take immediate action:

• Update to version 2.3.4 or later without delay.
• If patching is not possible, disable MCP functionality entirely.
• Restrict network access to the management interface using firewalls or VPNs.
• Review server logs and configuration directories for any unauthorized changes.

For more on securing your infrastructure, check out our guide on how to secure your nginx servers. Additionally, you may want to read about MCP security best practices to avoid similar pitfalls.

Conclusion: Act Now Before the Nginx-ui MCP Flaw Hits Your Network

Given the active exploitation and high CVSS score, this is not a vulnerability you can afford to ignore. The nginx-ui MCP flaw represents a clear and present danger to any organization using this popular web interface. By patching immediately, restricting access, and reviewing your logs, you can mitigate the risk. Remember, in the world of cybersecurity, a single missing line of code can open the door to disaster.

How a Signed Adware Operation Silently Disabled Antivirus on 23,000 Hosts Worldwide

A new signed adware operation linked to Dragon Boss Solutions LLC has been quietly disabling antivirus software on more than 23,000 endpoints globally, according to research from Huntress. This campaign, which uses a legitimate code-signing certificate and an off-the-shelf update mechanism, represents a significant threat to enterprise security. In this article, we break down the attack chain, the global impact, and what organizations can do to protect themselves.

Understanding the Signed Adware Operation

This signed adware operation was first observed by Huntress researchers in late March 2025, though the underlying loaders had been present on some systems since late 2024. The attackers used Advanced Installer to poll remote servers for MSI-based updates. Once delivered, a PowerShell script called ClockRemoval.ps1 executed with SYSTEM privileges, targeting security products from Malwarebytes, Kaspersky, McAfee, and ESET.

What makes this attack particularly dangerous is its use of a legitimate code-signing certificate, which helps it evade initial detection. The payload checks for admin status, detects virtual machines, and queries the registry for installed security products before deploying its full capabilities.

Attack Chain Details

After gaining initial access, the payload establishes five scheduled tasks and Windows Management Instrumentation (WMI) event subscriptions to maintain persistence. These tasks trigger at boot, logon, and every 30 minutes. A tight polling loop kills matching antivirus processes every 100 milliseconds for 20 seconds at startup, preventing security tools from initializing.

The script also strips registry entries, runs vendor uninstallers silently, and modifies the Windows hosts file to redirect antivirus update domains to 0.0.0.0. Defender exclusions are added for directories like DGoogle and EMicrosoft, which likely serve as staging areas for follow-on payloads.

Global Impact and Sinkhole Discovery

What elevated the threat was the discovery that a primary update domain in the operation’s configuration was unregistered. Huntress registered the domain first and pointed it to a sinkhole. Within 24 hours, 23,565 unique IP addresses requested instructions. Infections spanned 124 countries, with the US accounting for roughly 54% of connections, followed by France, Canada, the UK, and Germany.

The firm identified 324 infections on high-value networks, including 221 universities and colleges, 41 operational technology networks (including electric utilities), 35 government entities, and three healthcare organizations. This signed adware operation clearly targeted critical infrastructure and educational institutions.

Dragon Boss Solutions: The Company Behind the Attack

According to Crunchbase, Dragon Boss Solutions is based in Sharjah, United Arab Emirates, and describes itself as conducting “search monetization research.” Antivirus vendors have historically categorized their signature as adware with browser-hijacking functionality. While the immediate payload remains an antivirus killer, Huntress warned that the update infrastructure could deliver any payload type, including ransomware, cryptominers, or data theft tools.

For more on similar threats, check out our article on DeepLoad Malware Combines ClickFix With AI-Code to Avoid Detection.

How to Protect Your Organization

To defend against such attacks, ensure your antivirus software is up to date and consider using application whitelisting to block unauthorized executables. Monitor for unusual WMI event subscriptions and scheduled tasks, as these are common persistence mechanisms. Implement network segmentation to limit the spread of infections, and regularly review your code-signing certificate management to prevent abuse.

Additionally, consider using a robust endpoint detection and response (EDR) solution that can detect and block PowerShell-based attacks. Finally, educate your users about the risks of adware and the importance of reporting suspicious activity.

Conclusion

This signed adware operation highlights the evolving threat landscape where attackers use legitimate tools and certificates to bypass security. With over 23,000 hosts affected and a global footprint, organizations must remain vigilant. By understanding the attack chain and implementing proactive defenses, you can reduce the risk of falling victim to such campaigns.

Trump’s CISA Nominee Sean Plankey Withdraws, Leaving Agency Without Permanent Leader

The CISA leadership vacancy has deepened after Sean Plankey, President Donald Trump’s twice-nominated pick to lead the Cybersecurity and Infrastructure Security Agency, formally requested to withdraw his nomination. In a letter to the White House on Wednesday, Plankey cited an indefinite Senate holdup, stating it has “become clear” that lawmakers will not confirm him. This leaves the agency, tasked with defending federal civilian networks and critical infrastructure, without a permanent director for the foreseeable future.

Plankey’s decision comes more than a year after his initial nomination. According to reports from The New York Times and Politico, Senator Rick Scott (R-FL) blocked the nomination over a dispute unrelated to cybersecurity—specifically, a Coast Guard contract from Plankey’s tenure as a senior adviser to Coast Guard leadership. With the Senate unable to reach a majority vote, Plankey’s path to confirmation was effectively dead.

What Caused the CISA Leadership Vacuum?

The CISA leadership vacancy is not new. Since Madhu Gottumukkala departed in February after a tumultuous temporary tenure, Nick Andersen has served as acting director. Gottumukkala was appointed in May 2025 but left less than a year later, following several government shutdowns, furloughs, and budget cuts. The agency has struggled to maintain stability amid political headwinds.

Plankey’s withdrawal underscores a broader challenge: the Senate confirmation process for key cybersecurity roles has become increasingly politicized. A single senator’s hold can derail a nomination, leaving agencies like CISA in limbo. This means that critical cybersecurity decisions are being made by acting officials who lack the full authority of a Senate-confirmed leader.

Budget Cuts and Political Pressure on CISA

Adding to the turmoil, the Trump administration recently proposed slashing CISA’s budget by more than $700 million. The justification? Claims that the agency engaged in “censorship” during the 2020 election—a reference to its efforts to counter election misinformation. However, cybersecurity experts argue that these cuts could weaken the nation’s defenses against a rising tide of cyberattacks from state-sponsored groups and criminal networks.

Building on this, the agency has faced at least three government shutdowns in the past year, along with staff reductions and furloughs. Despite these challenges, CISA remains responsible for protecting civilian federal networks and coordinating with private sector partners on critical infrastructure security. The CISA leadership vacancy could not come at a worse time, as threats from ransomware, nation-state espionage, and hacktivism continue to escalate.

The Impact of a Vacant Director Seat

Without a permanent director, CISA may struggle to advocate effectively for its budget and priorities on Capitol Hill. Acting directors often lack the political leverage needed to push through long-term strategies. Furthermore, international partners may view a leaderless agency as a sign of instability, potentially undermining collaboration on cross-border cyber threats.

As a result, the White House faces pressure to nominate a new candidate quickly. However, with the Senate deeply divided, any nominee will likely encounter similar obstacles. For now, Nick Andersen continues to steer the ship, but his authority remains temporary.

What Happens Next for CISA?

The Trump administration has not commented on whether it will accept Plankey’s withdrawal request or announce a new nominee. A White House spokesperson declined to provide details, leaving the agency’s future direction uncertain. Cybersecurity professionals and policymakers alike are watching closely, as the CISA leadership vacancy could shape the nation’s cyber defense posture for years to come.

In the meantime, CISA must continue its mission with limited resources and no permanent leader. This situation highlights a recurring problem in U.S. cybersecurity governance: political infighting often takes precedence over national security needs. To learn more about how leadership gaps affect federal agencies, read our analysis on the risks of vacant director roles. For a deeper dive into CISA’s budget challenges, check out how funding cuts impact cybersecurity operations.

Ultimately, the CISA leadership vacancy is a symptom of a larger issue: the need for a more streamlined confirmation process for critical national security positions. Until that happens, agencies like CISA will remain vulnerable to political gridlock, even as cyber threats grow more sophisticated by the day.