jain.com — data centers, connectivity and security, analyzed daily

Tag: vulnerability management

  • FAZE Security Exits Stealth With $6M Seed and 50 Enterprise Logos

    FAZE Security Exits Stealth With $6M Seed and 50 Enterprise Logos

    TL;DR · 30-second read

    The Short Version

    A young cybersecurity company called FAZE Security came out of hiding on September 11 after building its product quietly. Its software turns loose automated attackers on a customer’s own websites and cloud systems, around the clock, to find weak spots before criminals do.

    It then breaks in to prove the weak spot is real, hands the problem to a named person, and keeps checking until the fix holds.

    FAZE says 50 large companies already pay for it, and investors have put in six million dollars. Most companies still get one security check a year.

    FAZE Security emerged from stealth on September 11, 2026 with $6 million in seed funding led by New Era Capital Partners, with participation from Lockstep VC. In an announcement distributed by PR Newswire, the company said it has 50 enterprise customers, several of them Fortune 500 firms, and roughly 20 times growth in annual recurring revenue over 18 months.

    The company operates from New York and Tel Aviv and was previously known as CYTRIX. It sells what it calls an Offensive Security Orchestration platform, built around an Agentic Red Team of autonomous software agents that continuously attack a customer’s web applications, application programming interfaces and cloud environments under defined guardrails.

    Executive Summary

    The announcement is a seed-stage milestone with an unusual shape. Most companies raise a seed round to go find customers. FAZE says it arrived at its public debut with 50 enterprise accounts already signed, which suggests the product was sold quietly for some time before the branding caught up with it.

    The product thesis targets a genuine and worsening operational problem. Automated scanners produce large volumes of findings ranked by theoretical severity, while annual penetration tests, in which human testers attempt to break in, produce a snapshot that ages from the moment it is written. Neither output tells a security team which of the thousands of open items an attacker could actually use today. FAZE’s pitch is that an agent that successfully exploits a weakness has answered that question by demonstration rather than by scoring.

    What the release establishes is commercial traction and investor conviction. What it does not establish is performance. The headline efficacy figures, close to zero false positives and more than 50 percent faster mean time to remediate, are presented as customer reports without a baseline, a sample size or a measurement method. Buyers evaluating the category should treat them as claims to be tested in a proof of concept, not as findings.

    The Backlog Is the Market

    Enterprise security teams have not been short of vulnerability data for a decade. They have been short of a defensible way to decide what to fix first. A scanner crawls an environment and flags known weaknesses against a database, then scores them on a standard severity scale. That scale describes how bad a flaw would be in the abstract. It says nothing about whether the flaw is reachable in your particular architecture, whether a control in front of it already neutralises the risk, or whether exploiting it would reach anything of value.

    The result is a queue that grows faster than engineering capacity retires it. Remediation work competes with feature work for the same developer hours, and a ticket labelled critical by a scanner carries no evidence to win that argument. Annual penetration testing, often driven by compliance obligations rather than by risk, does produce evidence, but only for the systems in scope on the week the testers were engaged. Between reports, the estate changes continuously and the report does not.

    FAZE is selling into the gap between those two instruments: the continuous coverage of a scanner combined with the demonstrated, working proof of a human test. That is a coherent product thesis and it is why several categories have converged on the same territory.

    Proof of Exploit Is the Product, Not the Attack

    The most substantive part of the company’s description is not the attacking. It is the loop that follows. FAZE says every finding arrives with working proof, an assigned owner and a remediation path, and that the system automatically re-tests until the exploit fails. That closes the accountability gap where most vulnerability programmes actually break down, which is between the moment a finding is raised and the moment someone can prove it is gone.

    It is worth being precise about what this does and does not do. The platform as described does not remediate anything. It ranks by demonstrated business impact, routes work to a named owner and verifies the fix. The fixing remains human engineering work. For buyers, that distinction matters when modelling return on investment, because the savings come from triage effort avoided and from faster closure, not from headcount replaced.

    The competitive moat the investor quote emphasises is the training data, described as proprietary attack material from thousands of white-hat hackers. That is a plausible advantage in a domain where public exploit corpora are thin and adversarial technique is tacit. It is also the hardest claim in the announcement for an outside party to evaluate, since neither the volume, the recency nor the coverage of that corpus is described.

    A Crowded Lane With No Agreed Scoreboard

    Autonomous offensive testing is not an empty field. Penetration testing delivered as a subscription service, breach and attack simulation, external attack surface management and continuous automated red teaming all approach the same buyer with overlapping promises, and the large vulnerability management incumbents have every incentive to add agentic testing to platforms already installed. A startup with $6 million has to win on depth of proof rather than breadth of platform.

    The category’s structural weakness is that nobody can compare vendors on results. There is no accepted benchmark for offensive testing accuracy, no standard definition of a false positive when the finding comes with a working exploit, and no neutral body publishing comparative detection rates. That vacuum is what makes self-reported efficacy numbers so common across the sector, and it is why a serious evaluation still comes down to running two tools against the same environment and counting what each one finds and misses.

    There is also an operational question specific to autonomous exploitation. Agents that genuinely exploit weaknesses in live web applications, interfaces and cloud accounts are performing actions that, without authorisation and controls, would be indistinguishable from an attack. FAZE says the agents operate within strict guardrails. The design of those guardrails, and the blast radius when one fails, is the thing a chief information security officer will ask about before the accuracy numbers.

    What a $6 Million Seed Signals

    Read as a market indicator, this round says less about FAZE than about where security capital is going. Investors are funding the layer that decides what to do with vulnerability data, not the layer that produces more of it. Detection has been commoditised; prioritisation backed by evidence has not.

    The growth figure deserves a careful reading. Twenty times annual recurring revenue growth over 18 months is striking as a multiple and uninformative as a quantity, because the starting base is not disclosed. A company moving from a small pilot base to a modest one produces that ratio easily. The 50 enterprise customers, including Fortune 500 accounts, are the harder number to manufacture, since large-enterprise security procurement involves vendor risk review and security questionnaires that most 18-month-old companies fail. That FAZE cleared those reviews at Fortune 500 accounts is the most load-bearing fact in the announcement.

    For buyers, the practical implication is timing. A seed-stage vendor at this size is early enough to negotiate favourable terms and early enough to carry real continuity risk. For competitors, the signal is that evidence-led prioritisation is being funded as a standalone category rather than a feature, and that the window to absorb it into existing platforms is narrowing.

    Background

    Enterprise vulnerability management has been built on two instruments for most of its history. Automated scanners, commercial since the late 1990s, compare systems against databases of publicly catalogued flaws and rank results on standardised severity scores. Penetration testing, in which authorised specialists attempt to break in, supplies evidence rather than inference but is periodic by nature, frequently scheduled annually because regulatory and contractual frameworks require it at that cadence. As enterprise estates moved to cloud platforms and continuous deployment, the interval between tests became the weak point: infrastructure now changes faster than the assessment cycle that is meant to describe it.

    FAZE Security, previously CYTRIX, is one of a number of companies applying autonomous agents to that interval, positioning itself in what it calls Offensive Security Orchestration. Israel has long been a concentrated source of offensive security engineering talent, and New York and Tel Aviv dual headquarters are a familiar structure for firms selling into United States enterprise security budgets. The company says it spent its stealth period building customer traction before making its public debut on September 11, 2026.

    Sources

    Source: FAZE Security emerged from stealth today with 50 enterprise customers, including several Fortune 500 companies, and ~20X ARR growth in 18 months. The company also announced $6M in seed funding led by New Era Capital Partners with participation from Lockstep VC, the company’s announcement of its public debut, funding round and reported customer traction, dated September 11, 2026.

  • Harness Debuts AI Agents to Fix Vulnerabilities at Machine Speed

    Harness Debuts AI Agents to Fix Vulnerabilities at Machine Speed

    On August 19, 2026, San Francisco-based Harness announced six new security capabilities — AI SAST, LLM Scan Orchestration, a Triage Agent, a Remediation Agent, a Zero-Day Agent, and virtual patching — all available now on its AI Software Delivery Platform. The agents are designed to compress the gap between the roughly six hours attackers now need to weaponize a disclosed vulnerability and the 50-plus days enterprises take on average to fix one.

    The launch landed the same day Palo Alto Networks unveiled its multi-vendor Frontier AI Critical Defense Program to protect critical infrastructure from AI-discovered vulnerabilities, and MarketsandMarkets projected the critical infrastructure protection market will grow from $160.28 billion in 2026 to $206.31 billion by 2031.

    Executive Summary

    Harness is betting that the vulnerability-response problem is no longer a detection problem but a speed problem. Frontier AI models — the most capable large language models — are being used by attackers to find and chain vulnerabilities faster than ever, with first exploits appearing as little as six hours after disclosure. Defenders are gaining the same scanning power: Harness cites Project Glasswing partners surfacing roughly 10 times more vulnerabilities with LLM-based scanning. But more findings without faster remediation just means a bigger backlog.

    The new agents cover the full vulnerability lifecycle inside the delivery pipeline itself: AI SAST pairs deterministic scanning with an AI layer that filters false positives and catches complex flaws like IDOR (insecure direct object references, where an attacker manipulates identifiers to access data they shouldn’t); the Triage Agent prioritizes what is actually exploitable; the Remediation Agent writes, validates, and opens a pull request with a fix; the Zero-Day Agent monitors disclosures around the clock and generates validated fixes often within minutes; and virtual patching shields production immediately with no code changes while the real fix is finished.

    Why it matters: as Harness application-security GM Rahul Sood put it, the same AI models helping customers ship software faster are what attackers use to exploit it faster — and the only way to close that gap is to make security a first-class part of the delivery pipeline rather than a disconnected process. The simultaneous Palo Alto Networks program launch suggests the whole industry has reached the same conclusion on the same day.

    The Six-Hour Exploit Window Breaks the Old Security Model

    The economics of vulnerability management were built on a comfortable assumption: defenders had weeks between a disclosure and real-world exploitation. Harness’s numbers — six hours to first exploit versus more than 50 days to an average fix — show that assumption is dead. When AI can read a vulnerability disclosure and generate a working exploit before most security teams have finished their morning stand-up, any process with human handoffs between scanning, ticketing, triage, and deployment is structurally too slow, regardless of how well each step is staffed.

    This reframes what security products have to sell. For two decades, the pitch was visibility: find more vulnerabilities. Harness’s own framing concedes that visibility now makes things worse — Project Glasswing partners finding 10x more vulnerabilities via LLM scanning simply produces a 10x bigger backlog if remediation speed stays flat. The scarce resource is no longer detection; it is validated, deployable fixes. Products will increasingly be judged on time-from-disclosure-to-deployed-patch, a metric most enterprises today cannot even measure.

    Security Is Collapsing Into the Delivery Pipeline

    Strategically, this launch is a land grab by a DevOps platform into application security territory. Harness’s argument is architectural: standalone scanners produce findings that must cross organizational and tooling boundaries to become fixes, and every boundary adds days. By putting scanning, triage, remediation, and deployment on one platform — with every agent working from the same reachability data, meaning analysis of whether vulnerable code is actually invoked in a given application — Harness claims fixes ship in hours without added headcount. The 2025 Traceable merger, July 2026’s Agent DLC governance launch, and the Kong and Google integrations show this has been a multi-year build, not a feature bolted on for a press cycle.

    The winners and losers logic is straightforward. Platform vendors that own the pipeline (Harness, and by extension GitHub, GitLab, and the cloud providers) gain a structural advantage over point-solution SAST and vulnerability-management vendors, whose findings now have to flow into someone else’s remediation loop. For buyers, the trade-off is the classic platform bargain: faster outcomes and fewer tools to manage, in exchange for deeper dependence on a single vendor.

    A Coordinated Industry Response — and a $206 Billion Market

    Harness did not announce alone. The same morning, Palo Alto Networks introduced the Frontier AI Critical Defense Program, described as a collaboration of leading technology providers to protect critical infrastructure against the rapid rise of AI-discovered vulnerabilities. When the largest pure-play security vendor organizes a multi-vendor defense program on the same day a DevOps platform ships machine-speed remediation agents, the signal is clear: AI-discovered vulnerabilities have moved from a research concern to the organizing threat model of the industry.

    The money follows. MarketsandMarkets projects the critical infrastructure protection market growing from $160.28 billion in 2026 to $206.31 billion by 2031, a 5.2% compound annual growth rate. That is steady rather than explosive growth — but the composition of that spend is what matters. Budgets built around perimeter appliances and manual patch cycles will be re-allocated toward automated response, and vendors positioned on the remediation side of the ledger stand to capture a disproportionate share of it.

    The Trust Problem: Machines Propose, Humans Still Approve

    Harness has kept a human in the loop at the critical moment — the Remediation Agent opens a pull request for a developer to review and approve rather than pushing fixes straight to production. That is the right call for adoption, but it also means the last mile of the process still runs at human speed. If AI agents generate 10x more validated fixes, code review becomes the new bottleneck, and enterprises will face pressure to auto-merge low-risk patches — a governance question this launch raises but does not resolve.

    Virtual patching, which shields production immediately without code changes, is the pragmatic hedge: it buys time at machine speed while humans finish the real fix. The risk to watch is complacency — virtual patches that quietly become permanent, accumulating an invisible layer of compensating controls. The enterprises that win with these tools will be the ones that treat machine-speed response as a bridge to actual remediation, not a substitute for it.

    Background

    Harness began as a continuous-delivery company and has grown into what it brands the AI Software Delivery Platform™ — automating the software lifecycle after code is written, from builds and testing through deployment and cost management. Customers such as United Airlines, Morningstar, and Choice Hotels use it to accelerate releases by up to 75% and cut cloud costs by 60%, and the company is backed by Goldman Sachs, Menlo Ventures, IVP, Unusual Ventures, and Citi Ventures. Its security push dates to the early-2025 merger with API-security firm Traceable and continued through 2026 with Agent DLC governance for AI coding agents and integrations with Kong and Google.

    The market backdrop is an arms race: the same frontier AI models that help developers ship faster let attackers find and chain vulnerabilities in hours, and let defenders surface an order of magnitude more findings than their patching processes were built to absorb. That dynamic — visibility outrunning remediation — is driving both vendor consolidation around delivery pipelines and industry-wide efforts like Palo Alto Networks’ new Frontier AI Critical Defense Program.

    Source: Harness Launches AI Agents for Machine-Speed Vulnerability Response — Harness press release via PR Newswire, August 19, 2026, with same-day context from Palo Alto Networks’ Frontier AI Critical Defense Program announcement and MarketsandMarkets’ critical infrastructure protection market forecast.

  • AI Breaches Now Cost $6M. IBM’s Data Says the Weak Spot Is Fixing, Not Finding

    AI Breaches Now Cost $6M. IBM’s Data Says the Weak Spot Is Fixing, Not Finding

    TL;DR · 30-second read

    The Short Version

    Criminals used artificial intelligence in about one in four serious hacking attacks last year, according to a yearly study backed by IBM. Many of those attacks used fake videos or voices to impersonate real people.

    Each of those attacks cost the victim about $6 million to deal with, roughly $1 million more than a typical break-in. Launching one can cost the attacker only thousands.

    The surprise: about half of companies use automated tools to spot attacks, but fewer than one in five use them to fix known weak spots before criminals get there.

    IBM said on July 29, 2026 that one in four malicious breaches in its 2026 Cost of a Data Breach Report were AI-enabled, which it described as a 56% increase over last year. Those breaches, mostly deepfake impersonation and AI-enabled malware, cost an average of $6 million, roughly $1 million more than the $4.99 million global average across all breaches in the study.

    The report, conducted by Ponemon Institute and sponsored and analyzed by IBM, covers breaches at 602 organizations worldwide between March 2025 and February 2026. A follow-on survey in May 2026 drew responses from 456 of those organizations.

    Executive Summary

    The headline number is the cost premium. By IBM’s account, AI-enabled breaches cost about 20% more than the average breach, while the attacks themselves are getting cheaper and faster to launch. IBM frames this as a shift in the economics of cyber risk: attacks that cost thousands to mount now produce losses in the millions.

    The more useful finding for security and infrastructure teams sits further down. More than half of organizations use AI agents, meaning software that can take actions on its own, to detect and contain threats. Only 18% use them for vulnerability management, the work of finding and fixing known flaws. IBM ties breach costs directly to the lag between discovering a problem and fixing it.

    The report also finds that more than 20% of organizations had a breach aimed at their AI models or applications. The most common causes were not exotic attacks on the models but ordinary weaknesses around them: exposed APIs and plug-ins, and misconfigured cloud environments running AI workloads.

    Thousands to Launch, Millions to Clean Up

    IBM’s central argument is that AI has widened a cost asymmetry that already favored attackers. Deepfake impersonation, in which synthetic audio or video of a real executive or colleague is used to trick staff into sending money or granting access, costs little to produce. AI-enabled malware can be adapted and scaled with less human effort. On the other side of the ledger, IBM puts the average AI-enabled breach at $6 million, against a global average of $4.99 million.

    That premium deserves careful reading. The release says AI-driven attacks were concentrated in financial services and energy, where average breach costs were $6.3 million and $5.2 million respectively. Some of the $1 million gap may therefore reflect which industries AI-enabled attackers targeted rather than anything intrinsic to AI-enabled techniques. The release does not say whether IBM controlled for sector or company size, so the premium is best treated as an observed average, not a measured effect of AI.

    The 56% increase is also stated without its base. Readers can infer that AI-enabled breaches were a meaningfully smaller share of the total a year earlier, but the release does not give last year’s figure.

    Finding Is Automated. Fixing Is Not.

    This is where the report’s numbers point to an operational conclusion. More than 50% of organizations reported using AI agents for threat detection and containment. Only 18% apply them to vulnerability management. In practice, many security teams have automated the alarm but not the repair: they can see an intrusion faster, but the known software flaws and misconfigurations that let attackers in are still patched on human timelines.

    IBM argues that this gap matters more as AI shortens exploit windows, the time between a weakness becoming known and attackers using it. Suja Viswesan, VP of IBM Security Software, put it directly: “When organizations have an extended gap between discovery and remediation, that imbalance shows up directly in breach costs.” IBM’s stated priority is to build remediation into development workflows and secure identity at runtime.

    The report’s other findings fit the same pattern of known, fixable exposure. Only 37% of breached organizations encrypt sensitive data both at rest and in transit, and just 34% have visibility into their cryptographic assets. The leading causes of AI-model breaches, compromised APIs and cloud misconfigurations, are well-understood problem classes rather than novel ones. Organizations using AI and automation in security operations cut breach costs by almost $2 million on average, per IBM, yet one in four have not adopted them at all. The release does not isolate the cost of slow remediation as a single number, so this conclusion rests on the deployment gap and the pattern of causes rather than a direct measurement. It is nonetheless the clearest reading of the data IBM published.

    AI Workloads Get Breached Through the Plumbing

    For data center and cloud operators, the most relevant statistic is that more than 20% of organizations reported a breach targeting AI models or applications. The two leading causes tied at 27% each: compromised APIs, applications or plug-ins, and cloud misconfigurations affecting AI workloads. APIs are the interfaces that let software systems talk to each other, and plug-ins extend what an AI application can reach. Both widen the surface an attacker can probe.

    This shifts attention away from attacks on model internals and toward the infrastructure surrounding them. AI workloads tend to sit in cloud environments with broad data access, many service connections and fast-changing configurations. Responsibility for those settings is typically split between the provider and the customer. When the weak point is a permissive storage setting or an unauthenticated endpoint, the fix is configuration discipline and access control, not a new class of AI security product.

    Critical Infrastructure and a Shift in Spending Intent

    IBM reports that 62% of AI-driven attacks targeted critical infrastructure sectors, with financial services and energy most affected. The company warns of cascading effects across supply chains and essential services. Energy is directly relevant to the AI buildout, since utilities and grid operators are central to powering new data center capacity. The release does not break down attacks on energy by subsector or describe any operational disruption.

    The follow-on research suggests awareness of advanced AI capabilities is moving budgets more than breaches do. Among surveyed organizations, 85% said they plan to increase security spending after learning about frontier AI cyber capabilities, compared with 64% that planned increases after experiencing a breach. These are stated intentions, not committed budgets, and 78% of follow-on respondents were aware of reports about frontier models such as Mythos. Three quarters said frontier AI threats are prompting them to rethink how agents are deployed across security operations. That suggests the remediation gap is recognized, even if it has not yet closed.

    Background

    The Cost of a Data Breach Report is a long-running annual benchmark produced by Ponemon Institute, a privacy and security research firm, and sponsored and analyzed by IBM. It surveys organizations that suffered breaches and estimates the full cost of each incident, including detection, containment, notification, lost business and recovery. Security leaders and insurers widely cite its averages when setting budgets and pricing risk.

    The 2026 edition is the first in which AI appears across nearly every finding. It covers AI as an attack tool through deepfakes and malware, as a defensive tool through agents and automation, and as a target through breaches of AI models and the cloud systems that host them. IBM is a hybrid cloud, AI and consulting company that also sells security software and services.

    Sources

    Source: IBM Study: One in Four Malicious Breaches are AI-Enabled, Costing Companies $6 Million on Average, IBM Newsroom’s July 29, 2026 announcement of its 2026 Cost of a Data Breach Report findings.

  • Gold Eagle’s 4-Agency Clearinghouse Shows AI Bug-Finding Now Needs a Triage Desk

    Gold Eagle’s 4-Agency Clearinghouse Shows AI Bug-Finding Now Needs a Triage Desk

    TL;DR · 30-second read

    The Short Version

    The White House has set up a central office, called Gold Eagle, where government agencies and the companies that run essential services like power, water and communications networks can pool security weaknesses that artificial intelligence finds in software.

    Why it matters: artificial intelligence can now search huge amounts of software for weak spots, and different groups often find the same ones. Gold Eagle is meant to sort that pile, drop the duplicates and tell defenders what to fix first. Taking part is voluntary.

    On July 14, 2026, the White House announced Gold Eagle, a federal clearinghouse for sharing AI-derived cybersecurity vulnerability information between government agencies, “American critical infrastructure companies” and “open-source software partners,” Covington & Burling’s Inside Privacy blog reported. The clearinghouse was established under Executive Order 14409, “Promoting Advanced Artificial Intelligence Innovation and Security,” which directed the Secretary of the Treasury to form it in consultation with the National Cyber Director, the National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA).

    According to the White House, Gold Eagle has already begun intake and prioritization of vulnerabilities “from across industries and sectors” and is coordinating “scanning verifications.” A day later, on July 15, CISA, the NSA and cyber agencies from the United Kingdom, the Netherlands and Japan issued joint guidance on coordinated vulnerability disclosure.

    Executive Summary

    Gold Eagle is a coordination body, not a scanning tool. Its stated purpose is to “leverage frontier AI capabilities to continue advancing faster than adversaries, reduce duplicative scanning efforts, and deliver prioritized and actionable threat and remediation information to defenders across the federal government and the private sector.” In practice, that means taking in software flaws surfaced by advanced AI models, verifying them, removing duplicates and handing defenders a ranked list of what to fix.

    The design matters because it signals where the government sees the problem. If AI has made finding vulnerabilities cheap and fast, the scarce resources become verification, prioritization and repair. For operators of critical infrastructure, including the data centers, network carriers and cloud platforms other sectors depend on, the practical question shifts from “what is vulnerable?” to “how quickly can we act on an authoritative must-fix list?”

    Participation is voluntary, and key operating details, including who has joined, how findings are protected and how quickly they are disclosed, had not been made public as of the announcement.

    Why AI Bug-Hunting Needs a Triage Desk

    Gold Eagle’s job, as described, is not to find vulnerabilities but to sort them. Executive Order 14409 structures it around four federal players, with Treasury leading in consultation with the National Cyber Director, the NSA and CISA, and tasks them to “coordinate and deconflict” the identification and remediation of software flaws. Deconflict is the telling word: it is what you do when many parties are working the same terrain and getting in each other’s way. The White House’s own framing, reducing “duplicative scanning efforts” and delivering “prioritized” information, points the same direction.

    The mechanism is straightforward. Frontier AI models, the most capable general-purpose systems from leading labs, can be pointed at large bodies of code and return candidate vulnerabilities in volume. When AI developers, agencies, security firms and independent researchers all scan the same widely used libraries, the same flaw can surface repeatedly, and every report lands on a maintainer or operator who has to check whether it is real. A clearinghouse that verifies once, collapses duplicates and ranks by severity turns a flood of raw findings into an ordered queue. The “scanning verifications” the White House says Gold Eagle is already coordinating are exactly that step.

    For critical infrastructure operators, the consequence is that the constraint moves downstream. A ranked advisory is only useful if the recipient can act on it: test a patch, book a maintenance window, push a firmware update (the low-level software built into hardware) to equipment that cannot simply be switched off. Gold Eagle can shorten the path from discovery to a prioritized warning; it cannot shorten an operator’s change-control process. The organizations that gain most will be those whose patching pipelines can absorb a faster, more authoritative stream of must-fix items. Those running always-on facilities with long approval cycles will feel the gap between knowing and fixing most sharply.

    Open-Source Maintainers Are the Pressure Point

    The announcement names “open-source software partners” alongside agencies and critical infrastructure companies, and that inclusion is significant. Much of the software running in data centers, telecom networks and industrial control systems is built on open-source components, freely available code often maintained by small teams or volunteers. If AI-driven scanning multiplies the number of credible reports, those maintainers carry the verification and repair burden before any operator can deploy a fix.

    The July 15 guidance addresses the other side of that exchange. CISA, the NSA, the UK’s National Cyber Security Centre, the Netherlands’ National Cyber Security Centre and Japan’s computer emergency response coordination center, five agencies from four countries, set out best practices for coordinated vulnerability disclosure: reporting a flaw privately to whoever can fix it and publishing details once a fix exists or an agreed deadline passes. The guidance urges software makers and online service providers to adopt transparent processes for receiving, evaluating and remediating reports. Read together, the two moves work both ends of the pipe: centralize intake of AI-found flaws, and press software producers to have a working front door ready when those findings arrive.

    Voluntary by Design, Concentrated by Nature

    Gold Eagle rests on voluntary collaboration with the AI industry and critical infrastructure operators, so its value will track who joins and how much they share. Information-sharing programs have long had to address the same hesitations: legal exposure, competitive sensitivity and the reputational cost of disclosing one’s own weaknesses. A new clearinghouse inherits those questions, and its early participation will be the clearest indicator of whether industry sees it as useful.

    A central store of verified, prioritized and not-yet-fixed vulnerabilities affecting critical infrastructure is also, by its nature, a high-value target. That is not an argument against the model, since coordination usually requires some concentration of information. But it makes the clearinghouse’s own security, access controls and disclosure timelines material design questions rather than administrative details, particularly for operators deciding whether to contribute findings about their own systems.

    Background

    The federal government has long encouraged private-sector sharing of cyber threat and vulnerability information, with CISA, part of the Department of Homeland Security, serving as the main civilian coordinator and the NSA contributing on the national security side. Critical infrastructure covers the systems society depends on, including energy, water, communications and information technology, which in turn rely on the data centers and networks that carry their traffic.

    The rise of highly capable AI models has changed the economics of finding software flaws: automated systems can now analyze large codebases at a scale that manual review cannot match. Gold Eagle, created under Executive Order 14409, is the Administration’s latest action on AI-enabled cybersecurity and an attempt to channel that capacity into a single, prioritized stream for defenders.

    Sources

    Source: White House Launches “Gold Eagle” AI Cybersecurity Clearinghouse, Inside Privacy (Covington & Burling), on the White House’s launch of a federal clearinghouse for AI-derived vulnerability information under EO 14409.

  • Gold Eagle’s Four-Agency AI Bug Hunt Shows Why Patching Is the Grid’s Real Limit

    Gold Eagle’s Four-Agency AI Bug Hunt Shows Why Patching Is the Grid’s Real Limit

    TL;DR · 30-second read

    The Short Version

    The White House has launched Gold Eagle, a program that uses the most advanced artificial intelligence systems to hunt for hidden flaws in the software that runs power grids, banks and the buildings that house the internet.

    Four parts of the federal government share the lead, working with private companies. Finding flaws faster is the easier half. Fixing them is harder: a power grid cannot simply switch off to install an update. The real test is how quickly operators can make repairs.

    The White House on Tuesday, July 14, launched the Gold Eagle Initiative, a cybersecurity vulnerability coordination clearinghouse meant to speed the identification, prioritization and remediation of software flaws across U.S. critical infrastructure, Industrial Cyber reported. The initiative was established under Executive Order 14409, the June 2 order on advanced artificial intelligence innovation and security.

    Gold Eagle is led jointly by the White House, the Treasury Department, the Department of Homeland Security through the Cybersecurity and Infrastructure Security Agency (CISA), and the Department of War, working with open-source software partners and critical infrastructure companies. It will use frontier AI, meaning the most capable current AI models, for faster exploit detection and prioritized threat sharing, and it has already begun collecting and prioritizing reported vulnerabilities across sectors.

    Executive Summary

    Gold Eagle is a coordination model, not a new regulation. The administration says it will draw on existing federal authorities and resources to cut duplicative vulnerability scanning, verify reported flaws once, and push prioritized, actionable remediation information to defenders in government and the private sector. The pitch is efficiency: many organizations currently scan for, triage and verify the same weaknesses independently.

    The significance for infrastructure operators lies in what happens after a flaw is found. AI-assisted discovery can increase the volume and speed of credible vulnerability reports reaching utilities, data center operators and their equipment vendors. For information technology systems, patching is routine. For the operational technology that controls power, cooling and physical processes, every fix competes with uptime, safety testing and vendor certification.

    That makes remediation capacity, not detection, the measure that will determine whether Gold Eagle materially reduces risk in the grid and data center sectors. The announcement describes the front half of that pipeline in detail and the back half only in general terms.

    A Clearinghouse, Not a Mandate

    The structure the administration describes is a central intake point for vulnerabilities: reports are collected, de-duplicated, verified and ranked, then routed to the organizations that must act on them. Frontier AI is positioned as the accelerant for both discovery and triage. Nothing in the announcement creates new reporting obligations for private operators; it frames Gold Eagle as a way to use “existing federal authorities and resources” more effectively and to “amplify collaboration between government and industry.”

    That design choice matters. A voluntary, collaboration-based model can move quickly because it does not wait on rulemaking, and the announcement says work is already under way. The trade-off is that its reach depends on which companies choose to participate and how much they share. The officials’ statements lean heavily on rhetoric, with references to a “wartime footing” and “unprecedented coordination,” but the announcement provides no participant list, volume figures or performance targets against which those claims can be measured yet.

    Why Patching, Not Finding, Is the Constraint

    The mechanism Gold Eagle describes covers identification, prioritization and verification, and then delivers “prioritized and actionable threat and remediation information to defenders.” The actual fix still lands on two groups outside the clearinghouse: the vendors who must write and validate a patch, and the asset owners who must install it. If frontier AI does what the administration expects and surfaces more credible flaws faster, the four federal leads will be increasing the flow into a pipeline whose downstream end they do not control.

    In operational technology, that downstream end is narrow. The programmable controllers, protection relays and supervisory systems that run a substation, and the building management, power distribution and cooling controls that keep a data hall online, are designed to run continuously for years. Updating them typically requires firmware validated by the equipment maker, testing against safety functions, and a scheduled maintenance window in which redundancy is temporarily reduced. A utility or colocation operator cannot absorb an unlimited number of those windows, and some legacy devices cannot be patched at all, leaving compensating controls such as network segmentation as the only near-term option.

    This is where Gold Eagle’s prioritization promise has real value, and also where it will be tested. A ranked list that tells an operator which of many findings is most exploitable in their environment helps them spend scarce maintenance windows well. An unranked or poorly contextualized flood of findings would do the opposite. The people most affected are control-system engineers at utilities, facility and critical-environment teams at data centers, and the product-security staff at industrial equipment vendors, all of whom have finite capacity to act on what Gold Eagle produces.

    What Grid and Data Center Operators Should Prepare For

    The operators best positioned to benefit are those that already know what they run. Prioritized advisories are only actionable if an organization can quickly match a flaw to a specific firmware version on a specific device, which requires an accurate asset inventory and, increasingly, software bills of materials from vendors. Operators without that inventory will receive the same intelligence but struggle to use it.

    Procurement is the second lever. Contracts for switchgear, uninterruptible power systems, cooling plant and building management platforms can specify how quickly a vendor must deliver a validated patch after a credible vulnerability is reported. If Gold Eagle accelerates disclosure, those terms become more consequential. Smaller utilities and regional data center operators with thin security staff are the most exposed to a gap between what they are told and what they can fix, and they may lean more on managed security providers and vendor support as a result.

    Open Source and the Question of Trust

    The inclusion of open-source software partners is notable, because much critical infrastructure software depends on open-source components maintained by small teams. AI-scale discovery could send those maintainers more verified reports than they can resolve, so the value of deduplication and verification upstream is substantial if it works as described.

    Participation also raises questions that private operators will weigh carefully. The Department of War is a co-lead alongside civilian agencies, and Treasury’s statement focuses on the financial sector. Companies deciding how much to share will want clarity on how data is handled, who sees it, how long vendors get before details circulate more widely, and what legal protections apply. None of that undercuts the initiative’s aims, but the answers will shape how much of the private sector’s visibility Gold Eagle can actually draw on.

    Background

    Coordinated vulnerability disclosure is the long-standing practice of reporting a software flaw privately to the vendor, giving time for a fix, and then publishing details so users can protect themselves. In the United States, CISA, created in 2018 within the Department of Homeland Security, plays a central role: it supports the CVE system that assigns identifiers to known flaws and maintains the Known Exploited Vulnerabilities catalog, which flags weaknesses attackers are actively using.

    Critical infrastructure spans energy, finance, communications, water and other sectors, and increasingly includes the data centers that support cloud and AI services. Much of it runs on operational technology, the industrial control systems that manage physical equipment, which historically lags office IT in patching because uptime and safety come first. Gold Eagle is the administration’s attempt to apply AI to the discovery and triage end of that process at national scale.

    Sources

    Source: US launches Gold Eagle initiative to boost cybersecurity vulnerability coordination, bolster critical infrastructure defense (Industrial Cyber): the White House’s launch of an AI-driven vulnerability clearinghouse under Executive Order 14409.

  • ShinyHunters Tied to Oracle PeopleSoft Exploit Wave

    ShinyHunters Tied to Oracle PeopleSoft Exploit Wave

    Cybersecurity Dive reports that the ShinyHunters extortion group has been linked to active exploitation of a critical vulnerability in Oracle PeopleSoft, the widely deployed human-resources, finance, and campus-management enterprise software. The story, published 13 June 2026, connects a named and prolific threat actor to a flaw in one of the most entrenched enterprise resource planning (ERP) platforms in government, higher education, and Fortune 500 back offices.

    Executive Summary

    PeopleSoft is the kind of software that most people never see but that quietly runs payroll, benefits, student records, and procurement at large institutions. A critical, exploitable flaw in that layer is a serious matter regardless of who is using it; the involvement of ShinyHunters, a group best known for bulk data theft and extortion, sharpens the concern because their business model turns vulnerabilities into public breach disclosures within weeks.

    For infrastructure and security teams, the report is a prompt to check patch levels, audit which PeopleSoft components are reachable from the internet, and review credential hygiene on service accounts. For executives, it is a reminder that the ERP suite — often treated as a stable, low-change system — is now firmly on the target list of financially motivated criminal groups.

    Why PeopleSoft Is a High-Value Target

    Oracle PeopleSoft sits at the center of workforce, finance, and student-information workflows at a large fraction of universities, state and local governments, and long-established enterprises. That means the databases behind it typically contain government identifiers, bank details, home addresses, dates of birth, and, in the campus-solutions modules, decades of student records. For an extortion group, that combination is unusually attractive: the data is sensitive enough to coerce a payment, and the victim organizations are often risk-averse public bodies with limited appetite for headlines.

    The platform is also structurally hard to defend. PeopleSoft deployments tend to be long-lived, heavily customized, and integrated with dozens of downstream systems, which makes patching a scheduled event rather than a same-week reflex. Internet-exposed components — application portals, integration brokers, and administrative consoles — often outlive the teams that first stood them up.

    What ‘Linked To’ Does and Does Not Mean

    The Cybersecurity Dive headline attributes exploitation to ShinyHunters, but attribution in this space is a spectrum. Analysts typically infer group involvement from infrastructure reuse, tooling, victim-negotiation patterns, or claims posted on leak sites. Each of those signals can be strong, but none is proof in the courtroom sense, and ShinyHunters itself has functioned at times as a brand adopted by multiple operators. Readers should treat the linkage as a credible working hypothesis rather than a settled fact until incident-response firms or Oracle publish technical indicators.

    The more actionable point is that a critical PeopleSoft flaw is being exploited in the wild. Whether the fingerprints belong to ShinyHunters, an affiliate, or a copycat, the defensive response is the same: assume opportunistic scanning against every exposed PeopleSoft instance and prioritize accordingly.

    The ERP Supply-Chain Angle

    Enterprise software vulnerabilities have a compounding effect that consumer bugs do not. A single PeopleSoft tenant may hold data for tens of thousands of employees, students, or retirees, and those individuals have no direct relationship with the vendor. When the platform is breached, the notification burden and reputational damage land on the customer institution, while the root cause sits upstream. This is the same dynamic that has driven regulator interest in file-transfer, identity, and ERP suites over the past several years.

    For infrastructure providers — data center operators, managed hosting firms, and cloud platforms that run PeopleSoft workloads — the incident is a reminder that shared-responsibility boundaries need to be explicit. Customers frequently assume that a hosted ERP is patched by the provider; providers frequently assume the customer owns the application layer. Exploitation campaigns thrive in that gap.

    What Defenders Should Do This Week

    Without a specific CVE cited in the summary, the durable guidance is procedural. Inventory every PeopleSoft instance, including test and training environments, which are routinely forgotten and rarely patched. Confirm that Oracle Critical Patch Updates are current and that internet-facing components sit behind a web application firewall or reverse proxy with authentication in front of admin paths. Rotate service-account credentials, review recent outbound traffic from PeopleSoft hosts for signs of bulk data egress, and confirm that database backups are both recent and offline-recoverable.

    Longer term, organizations running PeopleSoft should decide whether the application belongs on the public internet at all. Many of the historical breaches of ERP systems have started with a management interface that quietly became reachable during a migration and was never re-fenced.

    Background

    Oracle acquired PeopleSoft in 2005 after a protracted hostile takeover, folding the HR and campus-management pioneer into its enterprise applications portfolio alongside JD Edwards and, later, Siebel and NetSuite. Two decades on, PeopleSoft remains a mainstay in higher education and the public sector, where migration to newer cloud ERP suites is slow because of custom integrations, complex chart-of-accounts structures, and cautious procurement cycles.

    ShinyHunters emerged publicly in 2020 with the sale of stolen databases from a series of consumer web platforms and has since evolved toward extortion campaigns targeting cloud data platforms and enterprise SaaS. The group’s involvement with a core ERP suite would fit a broader industry trend of criminal operators moving from consumer targets toward the back-office systems that hold the most sensitive institutional data.

    Source: ShinyHunters linked to exploitation of critical flaw in Oracle PeopleSoft — Cybersecurity Dive report, 13 June 2026, on active exploitation of a critical PeopleSoft vulnerability attributed to the ShinyHunters extortion group.

  • CISA BOD 26-04 Moves Federal Patching Toward Risk-Based Prioritization

    CISA BOD 26-04 Moves Federal Patching Toward Risk-Based Prioritization

    On June 9, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) published Binding Operational Directive (BOD) 26-04, titled “Prioritizing Security Updates Based on Risk.” A Binding Operational Directive is a compulsory order to U.S. federal civilian executive branch agencies, and this one — as its title states — directs agencies to prioritize security updates according to risk rather than treating all patches alike.

    The directive continues an evolution in federal vulnerability management that began with fixed remediation deadlines and moved, over successive directives, toward focusing scarce patching capacity on the vulnerabilities most likely to be exploited.

    Executive Summary

    BOD 26-04 formalizes a shift that vulnerability-management practitioners have argued for over a decade: with tens of thousands of new vulnerabilities disclosed every year, no organization — not even a federal agency under mandate — can patch everything on a uniform clock. The rational alternative is to rank vulnerabilities by actual risk: whether they are being exploited in the wild, whether they sit on internet-facing or mission-critical systems, and what an attacker could reach through them.

    Why it matters beyond Washington: CISA’s directives bind only federal civilian agencies, but they have repeatedly become de facto standards for the private sector. The Known Exploited Vulnerabilities (KEV) catalog, created by BOD 22-01 in 2021, is now baked into commercial security tools, cyber-insurance questionnaires, and contract language far outside government. If BOD 26-04 follows the same path, risk-based patching mandates — with the documentation and telemetry they require — are a preview of what critical-infrastructure operators, federal contractors, and regulated industries should expect to be asked for next.

    A caveat on sourcing: this article is based on CISA’s publication of the directive and its stated title and purpose. The operational specifics — exact timelines, scoring methodology, and reporting requirements — live in the directive text itself, and we flag below what a one-line announcement leaves unanswered.

    From Compliance Clocks to Risk Math

    Federal patching policy has historically run on fixed deadlines. BOD 19-02 (2019) gave agencies 15 days to remediate critical vulnerabilities on internet-facing systems and 30 days for high-severity ones. BOD 22-01 (2021) refined the idea by creating the KEV catalog — a curated list of vulnerabilities with confirmed real-world exploitation, each carrying its own due date. Both approaches share a weakness: they treat severity scores or catalog membership as a proxy for risk, when the risk of any given vulnerability depends heavily on where it sits in a specific network and what it exposes.

    A directive built around risk-based prioritization acknowledges that reality. In plain terms, it means an agency should patch a moderately scored flaw on a crown-jewel system before a critically scored flaw on an isolated test box. That is how mature security teams already operate; the significance here is making it a matter of federal mandate rather than practitioner discretion. Mandating judgment is harder than mandating deadlines — which is precisely why the directive’s implementation details will determine whether it works.

    The Hidden Prerequisite: Knowing What You Own

    Risk-based prioritization has an unglamorous dependency: a complete, current inventory of assets and their exposure. You cannot rank vulnerabilities by risk if you do not know which systems are internet-facing, which hold sensitive data, and which are reachable from which. CISA has been building toward this for years — BOD 23-01 required asset visibility and vulnerability enumeration across federal networks — and BOD 26-04 is the logical next layer on that foundation.

    For infrastructure operators, this is the practical takeaway. Data-center, network, and cloud environments are dense with long-lived systems — hypervisors, building-management controllers, out-of-band management interfaces — where blanket patch deadlines were never realistic because patching means downtime windows and change-control risk. A risk-based regime is genuinely better suited to that world, but only for operators who have done the inventory and exposure-mapping homework first.

    The Template Effect on Critical Infrastructure

    CISA’s binding authority stops at federal civilian agencies; it cannot order a private colocation provider or utility to patch anything. Its influence, however, travels through softer channels: procurement requirements flow from agencies to their contractors and hosting providers, insurers and auditors adopt federal benchmarks because they are free and defensible, and sector regulators borrow CISA’s frameworks rather than inventing their own. KEV remediation status is already a common question in vendor security reviews.

    The likely trajectory is that risk-based patching expectations — documented prioritization decisions, exploitability-aware triage, evidence that high-exposure assets get fixed first — migrate into contracts and compliance frameworks over the next several years. Vulnerability-management and exposure-management vendors are natural beneficiaries, since operationalizing “risk-based” at scale is difficult without tooling that correlates threat intelligence, asset criticality, and network exposure. Organizations still running spreadsheet-driven patch cycles keyed to severity scores alone will find the gap widening.

    Background

    CISA has used Binding Operational Directives to steadily raise the floor of federal cybersecurity since the agency’s creation in 2018. BOD 19-02 imposed fixed remediation deadlines — 15 days for critical vulnerabilities on internet-facing systems — while BOD 22-01 created the Known Exploited Vulnerabilities catalog, shifting attention to flaws with confirmed real-world exploitation, and BOD 23-01 required agencies to build continuous asset and vulnerability visibility. Each directive has tended to ripple outward, shaping commercial security tooling and private-sector practice well beyond its legal reach.

    The broader industry context is a vulnerability-disclosure volume that has grown relentlessly for years, far outpacing any organization’s capacity to patch everything quickly. That arithmetic pushed the security field toward exploitability- and exposure-aware prioritization, and BOD 26-04 represents the federal mandate catching up with that practice.

    Source: BOD 26-04: Prioritizing Security Updates Based on Risk — CISA, the agency’s June 9, 2026 publication of a Binding Operational Directive on risk-based vulnerability prioritization for federal civilian agencies.

  • New MOVEit Flaws Spur Urgent Patch Warnings, Echoing the 2023 Breach Wave

    New MOVEit Flaws Spur Urgent Patch Warnings, Echoing the 2023 Breach Wave

    Newly disclosed vulnerabilities in MOVEit, the widely deployed managed file transfer (MFT) product from Progress Software, have prompted urgent warnings for organizations to apply patches, according to reporting by Cybersecurity Dive on May 3, 2026. MOVEit is used by enterprises and government agencies to move sensitive files between systems and partners — the same product family at the center of one of the largest mass-exploitation events on record in 2023.

    Executive Summary

    The core news is simple but consequential: security researchers and the vendor are urging customers to patch new flaws in MOVEit without delay. Managed file transfer software sits in a uniquely dangerous position — it is internet-facing by design, it holds or brokers an organization’s most sensitive data in transit, and it is often operated by IT teams rather than watched closely by security teams. That combination is exactly what made MOVEit the vector for the 2023 Cl0p ransomware group campaign, which compromised data belonging to thousands of organizations through a single zero-day.

    For infrastructure and security leaders, the announcement matters less for its specifics — which, based on the initial reporting, are limited — and more for what it triggers: an immediate patch-or-mitigate decision, a fresh look at third-party file-transfer exposure, and a reminder that attackers systematically revisit software classes that have paid off before. The window between disclosure of an MFT flaw and mass exploitation attempts has historically been measured in days, sometimes hours.

    Why File Transfer Software Keeps Getting Hit

    Managed file transfer products like MOVEit exist to do something inherently risky: accept connections from outside the network and exchange sensitive files — payroll data, health records, financial documents — with counterparties. That makes them internet-exposed, data-rich, and trusted, three attributes attackers prize. Unlike a compromised laptop, a compromised MFT server often yields immediately monetizable data with no lateral movement required.

    Attackers also learn from their own successes. The 2023 MOVEit campaign demonstrated that a single vulnerability in a widely deployed MFT product could compromise thousands of downstream organizations at once, and similar campaigns have targeted competing file-transfer products before and since. Once a product class proves lucrative, both criminal groups and researchers keep probing it — which is why new MOVEit vulnerabilities, whatever their individual severity, draw urgent attention.

    The Shadow of 2023

    In mid-2023, the Cl0p extortion group exploited a zero-day vulnerability in MOVEit Transfer to steal data from thousands of organizations worldwide, including government agencies, financial institutions, airlines, and universities. Many victims were not direct MOVEit customers at all — they were clients of payroll processors and other service providers who ran the software. That episode reframed MFT compromise as a supply-chain problem: your exposure depends not only on what you run, but on what your vendors run.

    That history explains the urgency of the current warnings. It does not, however, mean the new flaws are equivalent. The 2023 event involved a zero-day exploited before a patch existed; the current situation, as reported, involves disclosed vulnerabilities with patches or guidance available. Disclosed-and-patchable is a materially better position — but only for organizations that actually patch quickly, because disclosure also hands attackers a roadmap.

    The Patch Race and the Economics of Speed

    Once a vulnerability in an internet-facing product is public, exploitation is a race between defenders applying fixes and attackers scanning for laggards. Automated scanning means the entire exposed population can be enumerated within days. Organizations with mature vulnerability management — asset inventories that actually list every MOVEit instance, emergency change processes, and tested rollback plans — can close the window fast. Organizations that discover forgotten instances during an incident cannot.

    There is also a quieter economic story here for buyers. Repeated security events raise the total cost of ownership of any product: emergency patch cycles, incident retainers, insurance questionnaires, and customer security reviews all consume real money. Vendors in the MFT space are competing not just on features but on demonstrated security engineering and transparent disclosure — and enterprise buyers are increasingly scoring them on it.

    What Security Teams Should Do With Thin Early Reporting

    Early-stage vulnerability reporting is often light on detail, and the prudent response does not require full detail. The playbook is well established: identify every instance of the affected product, including ones operated by subsidiaries and third parties; apply vendor patches or mitigations on an emergency timeline; review logs for indicators of compromise rather than assuming patching closed the matter; and ask critical vendors in writing whether they run the product and what they have done. The 2023 experience showed that the organizations hurt worst were often those that learned of their exposure from an extortion note rather than from their own inventory.

    Background

    MOVEit is one of the most widely deployed managed file transfer products in enterprise and government environments, sold by Progress Software, a Massachusetts-based infrastructure software company. The product became a household name in security circles in mid-2023, when the Cl0p extortion group exploited a zero-day vulnerability in MOVEit Transfer to steal data from thousands of organizations worldwide in a single coordinated campaign — one of the largest mass-exploitation events on record, and one that reached many victims indirectly through service providers.

    Since then, the managed file transfer category as a whole has faced sustained attacker attention, with multiple vendors’ products targeted in similar data-theft campaigns. Progress has issued periodic security updates for the MOVEit line, and government cyber agencies routinely flag MFT vulnerabilities for priority remediation, reflecting the category’s outsized breach history.

    Source: New MOVEit vulnerabilities prompt urgent patch warning — Cybersecurity Dive’s May 3, 2026 report on urgent patch guidance for newly disclosed MOVEit file-transfer flaws.

  • CISA Flags Three More Cisco Flaws as Actively Exploited

    CISA Flags Three More Cisco Flaws as Actively Exploited

    The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has confirmed that three additional Cisco networking device vulnerabilities are being actively exploited, according to reporting published on 22 April 2026 by Cybersecurity Dive. The confirmation is the mechanism CISA uses to move a flaw from “theoretically dangerous” to “known to be used by attackers in the wild.”

    The practical effect is immediate for two groups: U.S. federal civilian agencies, which are bound by directive to remediate catalogued vulnerabilities by a set deadline, and the far larger population of enterprise, carrier and data center operators who use the catalog as a de facto triage list. The available source material is a headline-level summary; it does not itself specify which Cisco products, software versions or vulnerability identifiers are involved.

    Executive Summary

    CISA’s confirmation adds three more Cisco networking flaws to the pool of vulnerabilities with observed real-world exploitation. That designation matters because it changes the calculus for defenders. A vulnerability with a high severity score but no evidence of use can often wait for the next maintenance window. A vulnerability that attackers are already using cannot, because every hour of delay is measured against an adversary who has working code today.

    The reason this lands on an infrastructure publication rather than only a security one is placement. Cisco equipment frequently sits at the network edge — the routers, firewalls, VPN concentrators and switches that form the boundary between an organisation’s internal network and the public internet. That is precisely the gear that data centers, colocation providers, carriers and enterprises depend on for connectivity, and precisely the gear that is hardest to take offline for an unscheduled patch.

    It is also worth stating plainly what this announcement is not. A KEV listing is a statement that exploitation has been observed. It is not, on its own, a statement about how widespread that exploitation is, who is behind it, or whether any particular organisation has been affected. Treating the confirmation as an urgent triage signal is correct; treating it as evidence of a mass compromise event goes beyond what has been established.

    Why the Network Edge Keeps Returning to the Emergency List

    Edge network devices have become one of the most attractive targets in enterprise computing, and the reasons are structural rather than accidental. These appliances are internet-facing by design — a VPN concentrator that cannot be reached from the internet cannot terminate remote-worker sessions. They hold credentials, routing tables and traffic in cleartext at the point of decryption. And they sit upstream of nearly everything else, so an attacker who controls the edge does not need to defeat the controls behind it.

    They are also comparatively dark. Most organisations run endpoint detection software on laptops and servers, generating a continuous stream of telemetry that a security team can query. Purpose-built network appliances typically run closed operating systems that do not accept third-party agents. Defenders see syslog output and interface counters, not process trees. An intruder who establishes persistence in the firmware of a firewall can be very difficult to spot with the tools most organisations already own.

    This is why the pattern recurs. The 2023 mass compromise of Cisco IOS XE web management interfaces and the ArcaneDoor campaign against Cisco security appliances disclosed in 2024 were separate events with separate causes, but both illustrated the same underlying economics: a single working exploit against a widely deployed edge platform yields disproportionate access. Nothing in the current disclosure links these three flaws to those earlier campaigns, and it would be wrong to assume a connection. The category of risk, however, is the same one.

    What “Actively Exploited” Actually Establishes

    It is worth applying the same scrutiny to a government advisory that one would apply to a vendor press release. CISA’s catalog has a specific evidentiary bar: reliable evidence that a vulnerability has been exploited in the wild. That bar is meaningful and it is not trivially met. But it is a threshold test, not a measurement. Confirmation that exploitation occurred is compatible with a single narrowly targeted intrusion by a well-resourced state actor and equally compatible with commodity scanning at internet scale. Those two scenarios call for materially different responses.

    The publicly available material here does not distinguish between them. It does not indicate whether the three vulnerabilities are chained together, whether any require prior authentication, whether exploitation grants full device control or something narrower, or whether patched software is already available for all affected versions. Each of those variables changes the urgency and the remediation path substantially. Readers should be cautious of coverage — from any direction — that fills those blanks with inference.

    The defensible reading is procedural. If an organisation runs the affected platforms, the catalog entry is an instruction to verify version, apply the fix or documented mitigation, and check for signs of prior access. That instruction holds regardless of how the underlying campaign is eventually characterised, which is the practical virtue of the catalog as a triage mechanism.

    The Cost of Patching Infrastructure You Cannot Reboot

    The uncomfortable operational truth is that emergency patching of network infrastructure is expensive in ways that patching a fleet of laptops is not. A core router reload is a service interruption. High-availability pairs reduce but do not eliminate the risk, because failover itself can drop stateful sessions and because both members of a pair usually need the same update. In a colocation or carrier environment, those interruptions are governed by service level agreements with financial consequences, and change windows are often contractually constrained to specific overnight hours.

    The result is a genuine tension between two legitimate obligations: availability commitments to customers and security obligations to those same customers. Organisations with mature change management, tested rollback procedures and accurate asset inventories absorb an out-of-cycle patch cycle in days. Organisations without them discover during the incident that they do not know precisely which software versions are running where — and inventory gaps, not patch availability, are usually the binding constraint on response time.

    There is a second-order cost that is easy to underestimate. If a vulnerability permits persistence that survives patching, remediation is not patching but rebuilding: credential rotation, configuration review, and in some cases firmware reimaging or hardware replacement. Whether that applies here is unknown from the available material, but it is the question that determines whether this is a weekend of work or a quarter of it, and it is the first thing an operator should try to establish from the vendor’s own advisory.

    Market Consequences: Concentration Cuts Both Ways

    Cisco remains one of the largest suppliers of enterprise and service provider networking equipment, and that scale is the reason its vulnerabilities become industry events rather than vendor events. Concentration in critical infrastructure produces correlated risk: when a single platform is deeply embedded across banks, hospitals, carriers and government agencies, one exploit chain has systemic reach. This is a property of market structure, not a criticism of any particular engineering organisation — the same dynamic would apply to whichever vendor held the equivalent position.

    Concentration also has a defensive upside that is often ignored in the immediate coverage. A large installed base funds substantial security engineering, attracts sustained researcher attention, and supports a coordinated disclosure and patching apparatus that smaller vendors cannot match. Vulnerabilities found in widely deployed products are more likely to be found at all, and more likely to be fixed quickly once found. The relevant comparison for a buyer is not “a vendor with disclosed flaws versus a vendor without” but “a vendor whose flaws are found and fixed versus one whose flaws are found quietly by someone else.”

    For buyers and investors, the durable signal is therefore not the existence of these three entries but the response characteristics around them: time from discovery to patch, clarity of advisories, availability of compromise-detection guidance, and whether fixes reach older supported releases rather than only the newest. Those metrics differentiate vendors over multiple years. A single catalog addition, in a market where every major network vendor has appeared in the same catalog, does not.

    Background

    CISA established the Known Exploited Vulnerabilities catalog in November 2021 under Binding Operational Directive 22-01, replacing the previous practice of prioritising patches primarily by severity score. The premise was that severity ratings measure potential impact while exploitation evidence measures actual risk, and that defenders with finite maintenance windows should address the flaws attackers are demonstrably using first. Federal civilian agencies must remediate catalogued entries by assigned deadlines; the catalog has since been adopted far more broadly as a prioritisation standard across private industry.

    Cisco has been one of the dominant suppliers of enterprise and service provider networking equipment for decades, with routers, switches, firewalls and VPN platforms embedded across carriers, data centers, financial institutions and government networks. That installed base makes its products both a persistent target for well-resourced adversaries and a focus of intensive security research. The recurring pattern of internet-facing network appliances becoming intrusion vectors is an industry-wide condition rather than a single-vendor one, driven by the fact that this equipment must be reachable to do its job while running closed operating systems that resist conventional monitoring.

    Source: CISA confirms exploitation of 3 more Cisco networking device vulnerabilities — Cybersecurity Dive, 22 April 2026, reporting CISA’s addition of three further Cisco networking flaws to its Known Exploited Vulnerabilities catalog.