Project Glasswing is a genuine step change in cybersecurity. Anthropic’s Claude Mythos Preview model has reportedly uncovered thousands of previously unknown vulnerabilities across major operating systems, browsers and critical software, including a 27‑year‑old OpenBSD bug, a 16‑year‑old FFmpeg flaw and chained exploits in the Linux kernel that lead to full system compromise. It is powerful enough that Anthropic has decided not to release the full Mythos model broadly, positioning Glasswing as a tightly controlled, “defense‑first” initiative with a limited consortium of hyperscalers, security vendors and financial institutions.

So, is the glass half full or half empty?

• Glass Half Full: Defenders finally have AI that can find and help fix vulnerabilities at machine speed.
• Glass Half Empty: The same class of capability will eventually be in the hands of attackers, compressing the time from discovery to weaponization to minutes, not months.

Both are true. But focusing only on vulnerabilities misses a bigger problem: the world is already full of exposed configuration mistakes that today’s understaffed security teams struggle to find and fix.

And AI will accelerate the exploitation of those just as surely as it accelerates vulnerability discovery.

The Real Bottleneck Isn’t Just Patching—It’s Everything Around It

Most critical infrastructure and government environments are already behind on patching for entirely understandable reasons: legacy systems, fragile integration chains and change windows negotiated with business owners who fear outages more than Common Vulnerabilities and Exposures (CVE). Even if Mythos‑class models hand defenders a perfectly prioritized list of zero‑days, many organizations cannot patch fast enough to keep up.

But underneath the vulnerability backlog is something even more basic:

• Secure configuration management at scale—across DNS, identity, network, cloud, OT and application stacks—is still largely manual and error‑prone.
• Security teams are chronically understaffed, while being pressed to “move at the speed of the business.” The result is predictable: shortcuts, drift and blind spots.

In DNS alone, we see this every day. In a recent assessment of nine major corporations, every single one had DNS misconfigurations that could be exploited. Two had critical exposures that would be trivial for a competent threat actor to use. None of these issues required a zero‑day; they were the outcome of ordinary operational pressure over time.

DNS as the Canary: Lame Delegations, NIST SP 800‑81 and Sitting Ducks

DNS is a perfect example of why “vulnerabilities versus misconfigurations” is a false dichotomy.

National Institute of Standards and Technology (NIST) Special Publication (SP) 800‑81 has only recently been updated after years of relatively static guidance, reflecting a growing recognition that DNS is a critical security control, not just plumbing. The refreshed guidance sharpens expectations around architecture, logging and controls for issues such as lame delegations, dangling records and abuse of recursive resolvers, and is rapidly becoming the baseline for DNS security best practice, including in the European Union’s NIS2 technical guidance on DNS and protective DNS controls. It is the reference many regulators and operators reach for when they ask, “What does secure DNS actually mean in practice?” At the same time, recent campaigns such as the Sitting Ducks hijacks by Russian‑nexus actors like Vacant Viper and the broader “Vipers” and “Hawks” crews—which have abused misconfigured name‑server delegations and other DNS hygiene failures to hijack tens of thousands of domains, including household brands—underline how far real‑world practice still lags this guidance.

Infoblox and Eclypsium’s Sitting Ducks research showed that simple DNS misconfigurations, especially lame delegations, allow attackers to hijack domains without ever touching the registrar account. At any given time, over one million domains are exploitable; hundreds are actively hijacked every day. Follow‑on work found roughly 800,000 vulnerable domains and about 70,000 confirmed hijacks, driven primarily by misconfigured name server settings. Other studies estimate that on the order of 10 to 14 percent of delegations are lame in large domain samples.

Those same research threads, and subsequent Infoblox work, highlight how:

• Dangling CNAMEs and other dangling DNS records are pervasive, leaving “forgotten” links to expired cloud resources or domains that attackers can reclaim for phishing, malware delivery and traffic distribution systems (TDSs).
• Misconfigurations like lame delegations are not assigned CVEs and often sit outside the vulnerability management process entirely, so agencies and enterprises systematically under‑prioritize them compared to software bugs.

In other words, the world doesn’t just have a vulnerability problem. It has a configuration hygiene problem on top of that, and the latter is at least as attractive to attackers, precisely because it is so often invisible to defenders.

Now imagine Mythos‑class models and their successors applied not only to code, but to DNS zones, cloud control planes, routing policies and identity and access management (IAM) graphs. They won’t just find zero‑days; they’ll find every misconfiguration that matters and automatically chain them into practical attack paths.

Why We Need an AI Automation Strategy for Both Vulnerabilities and Configurations

If you accept that:

1. AI will make discovering exploitable conditions (bugs and misconfigs) cheap and fast, and
2. You cannot rely on vendors always shipping a patch in time, nor on your own organization always having a convenient maintenance window, then the response cannot simply be “patch faster.”

Organizations need a holistic AI‑driven automation strategy that treats vulnerabilities and configurations as part of the same risk fabric:

1. Unify Visibility and Risk Modeling

• Correlate software vulnerabilities with DNS hygiene, cloud posture, network exposure and identity misconfigurations into a single view of “ways an attacker can win.”
• Include external attack surface and DNS risks like lame delegation, Sitting Ducks conditions and dangling CNAMEs alongside traditional CVEs.

2. Use AI To Discover and Prioritize Issues, Not Just To Scan Code

• Continuously analyze configs, logs and external DNS data to highlight misconfigurations that materially expand blast radius, not just “non‑compliant” settings.
• Ask models to reason about attack paths: “Given this set of DNS, network and identity issues, what’s the shortest route to domain admin or data theft?”

3. Automate Mitigation—Especially when Patching Isn’t Possible

You won’t always get a vendor patch in time, and even when you do, you won’t always have the change window to deploy it. That’s where AI‑assisted automation and policy come in:

• For DNS: Automatically detect and remediate lame delegations, clean up dangling records and enforce safe delegation patterns with minimal human approval.
• For Network and Identity: Automatically tighten segmentation, DNS and web filtering, and access controls around assets affected by high‑risk vulnerabilities or misconfigurations.
• For Applications and Cloud: Generate and deploy safe, reversible configuration changes (e.g., disabling risky plugins, tightening security groups, revoking stale trust relationships) under human‑defined guardrails.

The goal is not “no humans,” but no heroics: let humans decide strategy and exceptions, while AI does the drudge work of detection, enrichment, change generation and verification.

4. Bake Safety and Governance into the AI Layer Itself

• Treat powerful security models as high‑risk infrastructure, with their own access controls, logging and red‑team testing.
• Ensure AI‑driven automations are explainable, reversible and tested in staging before touching production.

Planning for the Dam to Break—and a Concrete First Step

Anthropic is trying to be responsible in how it exposes Mythos‑class capability, and that’s commendable. But we should be honest: hoping that one vendor “holds the line” is not a strategy.

History tells us that:

• Capabilities leak and are replicated. Rivals are already racing to match or surpass Mythos in cyber‑relevant skills.
• Governments and critical infrastructure will not all be invited into closed initiatives like Glasswing. Most of the world’s vulnerable infrastructure will remain outside that inner circle for a long time.

At some point, the dam breaks: Mythos‑class offensive capability, or something close enough, will be broadly available. When that happens, attackers won’t need deep expertise to find exploitable DNS misconfigurations, dangling CNAMEs, legacy protocol exposures or unpatched zero‑days. They’ll ask their AI, and it will oblige.

The only sustainable response is for defenders to embrace the same level of automation and intelligence, and to point it not just at software vulnerabilities but at the sprawling universe of configuration risk that makes those vulnerabilities so devastating.

AI will absolutely help us find and fix more bugs. But if we want the glass to be more than half full, we have to use it to clean up the misconfigurations too, starting with an honest DNS health check against baselines like NIST SP 800‑81 and NIS2 guidance, and then building an AI‑assisted operations strategy that continuously enforces that hygiene.

A practical first step is to use Infoblox Inspect to assess how well your current DNS infrastructure and security controls actually protect you. Infoblox Inspect is a lightweight, complimentary assessment that:

• Validates DNS infrastructure and configuration against best practices
• Tests your ability to block high‑risk and malicious domains, including TDS, domain generation algorithms (DGAs), phishing and command-and-control (C2) infrastructure
• Surfaces gaps in both security controls and DNS hygiene that attackers routinely exploit
• Delivers an executive‑ready report you can map directly to NIST 800‑81 and NIS2‑aligned expectations, and use to drive both remediation and your AI operations roadmap

Glasswing and Mythos Preview show us what is now possible—for defenders and for attackers. The question is whether we use the same level of intelligence to finally bring DNS and configuration hygiene up to the standard our critical infrastructure deserves.

Public Sources