Citrix NetScaler Authentication Bypass: The 9.3 Severity Flaw

Citrix has rolled out patches for two vulnerabilities in its NetScaler ADC and NetScaler Gateway products. The more serious of the two, tracked as CVE-2026-19490, carries a CVSS score of 9.3 and is described as an authentication bypass using an alternative path.

This Citrix NetScaler authentication bypass impacts appliances configured as a gateway (SSL VPN, ICA Proxy, CVPN, RDP Proxy) or an AAA virtual server. The worst part? It can be exploited by remote, unauthenticated attackers without any user interaction, according to cybersecurity firm Rapid7.

Which NetScaler Versions Are Vulnerable?

Per Citrix’s advisory, the security defect impacts a wide range of NetScaler ADC and NetScaler Gateway versions. The list includes 14.1-43.56 or later, 14.1-66.68-FIPS or later, 14.1-43.55 or earlier, 13.1-61.28 or later, 13.1-61.27 or earlier, and 13.1 FIPS.

If you’re running any of these, you need to act. The fixed versions are:

• 14.1-73.32
• 13.1-63.21
• 14.1-73.32 FIPS
• 13.1-FIPS and 13.1-NDcPP 13.1-37.277

These builds also contain fixes for CVE-2026-19489, a high-severity memory overflow issue. That one could lead to unexpected behavior or denial-of-service (DoS) if SIP ALG is enabled at an LSN group configuration.

Secure Private Access Hybrid Deployments Also Affected

Citrix notes that Secure Private Access Hybrid deployments using NetScaler instances are also affected by these vulnerabilities. Customers need to upgrade these NetScaler instances to the recommended builds to address the issues.

Why Experts Expect Quick Exploitation

Rapid7 says there are currently no indicators that threat actors are exploiting the authentication bypass issue. But that’s likely to change. NetScaler’s critical role within enterprise systems makes it an attractive target for hackers.

The firm points out that NetScaler ADC and NetScaler Gateway are widely deployed enterprise networking products commonly positioned at or near the network perimeter. NetScaler ADC provides application delivery, traffic management, load balancing, SSL/TLS offloading, and application security capabilities, while NetScaler Gateway provides secure remote access and VPN functionality.

Given that NetScaler appliances are typically deployed in enterprise DMZs and are publicly accessible, Rapid7 expects threat actors to exploit the critical bug shortly. The company’s advice is blunt: organizations should prioritize patching affected systems on an emergency basis, since Citrix products are high-value targets that tend to quickly see exploitation in the wild.

This isn’t the first time Citrix NetScaler has been in the spotlight for security issues. Past incidents have shown that attackers move fast when it comes to these devices. For a broader look at how similar flaws have played out, check out our coverage of the critical GitLab flaw exploited shortly after disclosure and the previous Citrix NetScaler HTTP/2 bomb attack.

What Should Organizations Do Now?

The message from security researchers is clear: don’t wait. If your organization uses Citrix NetScaler ADC or Gateway, verify your version and apply the patches immediately. The authentication bypass issue is too dangerous to leave unaddressed, especially given the public accessibility of these devices.

For those who need more context on how similar vulnerabilities have been handled, our article on the exploitation of a fresh Citrix NetScaler vulnerability offers useful background on the threat landscape surrounding these products.

Stay ahead of the curve by keeping your NetScaler deployments up to date and monitoring Citrix’s security advisories regularly. The window for safe patching may be smaller than you think.

NadMesh: A New Threat in the AI Service Landscape

In early July, security researchers spotted a new Go-based botnet named NadMesh. It’s not your run-of-the-mill malware. This one has a singular focus: hunting exposed AI services to pilfer cloud keys and Kubernetes tokens. The operator’s own dashboard reportedly shows 3,811 unique AWS keys already harvested.

That’s a staggering number. And it underscores a growing problem — teams stand up AI tools fast, often skipping security configurations. NadMesh exploits that haste.

How NadMesh Finds Its Targets

The botnet uses a Shodan harvester to keep its scan queue stocked. It’s not scanning randomly. It targets specific platforms: ComfyUI, Ollama, n8n, Open WebUI, Langflow, and Gradio. These are the image generators, local model runners, and workflow builders that developers love for their speed and ease.

But speed comes at a cost. Many of these services are deployed without authentication or proper network segmentation. That makes them low-hanging fruit for attackers.

The Role of Shodan in NadMesh’s Operations

Shodan is a search engine for internet-connected devices. NadMesh uses it to identify vulnerable AI services exposed to the internet. Once found, the botnet moves in, exploiting known weaknesses or misconfigurations.

This isn’t a sophisticated zero-day exploit. It’s basic hygiene failure — services left open, default credentials, unpatched versions. NadMesh simply capitalizes on that.

What NadMesh Steals and Why It Matters

The primary targets are AWS keys and Kubernetes tokens. These credentials grant access to cloud infrastructure. With them, an attacker can spin up resources, exfiltrate data, or launch further attacks.

The 3,811 AWS keys on the operator’s dashboard represent real organizations. Each key is a potential entry point. And Kubernetes tokens? They can unlock entire clusters, exposing sensitive workloads and secrets.

This isn’t just about data theft. It’s about control. Once inside, attackers can use these resources for cryptomining, ransomware, or as a launchpad for bigger operations.

Protecting Your AI Services from NadMesh

So, what can you do? Start by auditing your exposed services. If you’re running ComfyUI, Ollama, or any of the targeted platforms, check if they’re accessible from the internet. They shouldn’t be.

• Restrict access with firewalls or VPNs.
• Enable authentication, even for internal tools.
• Regularly update to patch known vulnerabilities.
• Monitor network traffic for unusual activity.

These steps sound basic, but they’re often overlooked. NadMesh thrives on that oversight.

Securing Cloud Keys and Kubernetes Tokens

Beyond service exposure, pay attention to credential management. Rotate AWS keys regularly. Use short-lived tokens for Kubernetes. Implement least-privilege access. If a key is compromised, limit the damage.

Consider using secrets management tools. They centralize control and add an extra layer of security. It’s not foolproof, but it raises the bar.

The Bigger Picture: AI Security Is a Moving Target

NadMesh is a symptom of a larger issue. AI services are proliferating faster than security practices can keep up. Teams deploy tools for productivity, but they forget the basics.

The result? A botnet like NadMesh finds thousands of exposed services and walks away with thousands of cloud keys. It’s a wake-up call.

For more on securing your infrastructure, check out our guide on protecting cloud environments from botnet attacks. And if you’re using Kubernetes, you might want to read about Kubernetes security best practices.

Also, stay informed on AI service vulnerabilities to keep your deployments safe.

Don’t wait for the next NadMesh. Secure your AI services today.

Milan Startup’s Bet: Assume the Breach, Then Trap the Attacker

Most security tools try to keep hackers out. Beelzebub, an Italian AI-native cybersecurity startup, operates on a darker assumption: the bad guys are already in. And instead of just detecting them, the company wants to trap them.

That bet just got a serious cash infusion. The Milan-based firm announced it raised €3 million (roughly $3.4 million) in a seed round led by VC United Ventures. With this latest injection, the company’s total funding now stands at $3.8 million.

The Beelzebub Platform: A Closed Loop for Intruders

Founded in 2025, Beelzebub has built a platform that fuses red-team and blue-team tactics into a single response system. The core idea is simple: if you can’t stop every intrusion, make the intrusion itself a losing game for the attacker.

The platform’s approach is built on a few key pillars:

• Continuous adversary emulation – It actively probes for attack paths before real criminals exploit them.
• Runtime deception technology – LLM-powered traps that lure attackers into a controlled environment.
• Autonomous threat intelligence – When an attack is intercepted, the system automatically converts it into actionable defenses.
• AI analyst – Dissects malware, generates full incident reports, and contains affected systems instantly.

The whole loop is designed to isolate a threat, trigger incident response, and learn from the encounter — all without waiting for a human analyst to catch up.

On-Premises for the Paranoid (and the Regulated)

One of the more interesting angles is deployment flexibility. The platform works as a SaaS, but it can also run entirely on-premises. That’s a critical feature for organizations in sensitive environments — think critical infrastructure or government-adjacent sectors — that can’t send data to cloud-based tools.

NIS2-Ready and Backed by a Global Threat Intel Network

Beelzebub isn’t just building traps; it’s also plugged into a live intelligence feed from over 60 independent researchers worldwide. That’s a significant network for a startup that’s barely a year old.

The platform is also designed to be NIS2-ready out of the box. For European organizations scrambling to meet the EU’s updated cybersecurity directive, that’s a selling point that could open doors.

Where the Money Goes: Rome, San Francisco, and a Bigger Research Team

Founder and CEO Mario Candela has clear plans for the fresh capital. The company will expand its research team, open new offices in Rome and San Francisco, and aggressively pursue clients across Europe — with a focus on NIS2-regulated organizations.

“Cybersecurity is a nonstop battle, and one that humans can no longer fight alone,” Candela said. “AI-powered attackers are too powerful, too competent, too fast, and too numerous, meaning the only way to fight back is at the same pace and intensity.”

He emphasized that the product adapts to new malware and stays updated to match the current state of the most sophisticated attacks.

The Bigger Picture: AI vs. AI in Cybersecurity

Beelzebub’s approach reflects a broader trend in the industry. As attackers weaponize AI to automate their campaigns, defenders are being forced to respond with AI of their own. The days of relying solely on human analysts to spot and stop intrusions are fading fast.

The funding round also signals growing investor confidence in deception-based defense. It’s a niche but increasingly vital segment of the market, and Beelzebub’s hybrid red/blue team model gives it a distinctive position.

For those tracking the space, it’s worth watching how the company scales its threat intelligence network and whether its on-premises offering gains traction with NIS2-regulated firms.

Related coverage: AI-powered email security funding and composable security operations platforms have also drawn significant investment recently.