Jordan: A CVSS 10.0 authentication bypass in Cisco SD-WAN. Actively exploited. CISA deadline is Sunday. If you're running Catalyst SD-WAN and you haven't patched yet, stop what you're doing.

Alex: Welcome to Cleartext. It's Friday, May 15th, 2026. I'm Alex Chen.

Jordan: And I'm Jordan Reeves.

Alex: Today we're covering a week that felt like a stress test for the entire security stack. Two critical zero-days with active exploitation, a ransomware hit on one of the world's largest manufacturers, a supply chain attack that reached inside OpenAI, and a ransom payment that bought exactly what ransom payments almost always buy — nothing. We'll also get into the Pentagon's new framing around AI as revolutionary warfare and what that means if you're a CISO in the defense supply chain. Let's get into it.

Jordan: Let's start with the most urgent thing on every patching team's plate right now. CVE-2026-20182. Critical authentication bypass in Cisco Catalyst SD-WAN Controller and SD-WAN Manager. CVSS 10.0. Exploited in the wild by what Cisco is calling a highly sophisticated threat actor. CISA has this on the KEV catalog with a May 17th remediation deadline for federal agencies — that's Sunday.

Alex: And this is the second CVSS 10.0 SD-WAN bug exploited this year from Cisco. At some point that pattern becomes a vendor conversation, not just a patching conversation. If you're running Catalyst SD-WAN — on-prem or cloud — this is not a "schedule it for next week" situation.

Jordan: Right alongside it, CVE-2026-42897 in on-premises Microsoft Exchange Server. CVSS 8.1, cross-site scripting vulnerability, actively exploited via crafted emails targeting Outlook on the web. Affects Exchange 2016, 2019, and Subscription Edition. Exchange Online is clean.

Alex: The uncomfortable part here is there's no permanent fix yet. Microsoft has published temporary mitigations, but that's where you are — mitigations, not a patch. If you're still running on-prem Exchange, you need to apply those mitigations today and have a monitoring posture that assumes someone is probing your environment. The fact that it's delivered via email makes the blast radius enormous.

Jordan: Two zero-days in active exploitation on a Friday. Your weekend ops team is going to have opinions about you.

Alex: Moving to the breach side of the week, and there's a lot of it. Foxconn confirmed a ransomware attack hit its North American manufacturing facilities. The Nitrogen ransomware group is claiming responsibility and alleging they exfiltrated 8 terabytes of data — more than 11 million files — belonging to Foxconn's top customers.

Jordan: Context here matters. Foxconn is one of the largest contract manufacturers on the planet. Apple, Google, Dell, Sony — the customer list reads like a Fortune 100 reunion. If Nitrogen's claims hold up, this isn't just a Foxconn problem. This is potentially a data exposure event for companies whose products are manufactured there. Procurement data, engineering specifications, customer information — that's the universe of what 8TB from a manufacturer could contain.

Alex: The supply chain risk conversation just got very concrete for a lot of boards. CISOs need to be asking two questions right now. First, does your organization have a manufacturing relationship with Foxconn? Second, what's your contractual and notification exposure if your data is in that tranche? This is also not an isolated incident. We're on pace for over 600 ransomware attacks against manufacturers in 2026 alone. The sector is under siege and the adversaries know that operational disruption creates payment pressure fast.

Jordan: And then there's the OpenAI supply chain story, which is a different flavor but equally instructive. Two OpenAI employee devices were compromised through malicious packages embedded in the TanStack ecosystem across npm and PyPI. OpenAI rotated code-signing certificates as a precaution and says no user data or production systems were affected.

Alex: The "no production systems affected" line is important, but let's not let it obscure the real takeaway. If OpenAI — a company that employs some of the most technically sophisticated people in the industry and is acutely aware that it's a high-value target — can have developer devices compromised through package poisoning, this is a universal exposure. The attack surface here is your software supply chain, specifically your developers' toolchains.

Jordan: The TanStack campaign was broad. Hundreds of packages across two major repositories. The technique isn't new, but the scale is. CISOs need to be asking their engineering leadership: what's our dependency audit posture? Are we pinning versions? Do we have code-signing verification in our CI/CD pipeline? These are not exotic questions anymore.

Alex: Now for the ransom payment story that I think deserves more attention than it's getting. Instructure, the company behind the Canvas learning management platform, paid a ransom to ShinyHunters after a breach that involved children's personal data. They then communicated to victims that they had received digital confirmation of data destruction.

Jordan: Digital confirmation of data destruction. I want to sit with that phrase for a moment. There is no mechanism that provides reliable confirmation of data destruction from a ransomware group. Full stop. The industry consensus, backed by years of cases, is that paying does not ensure deletion. ShinyHunters in particular has a documented history of re-extorting victims.

Alex: The board-level dimension here is significant. When the breached data belongs to minors, the legal and regulatory exposure is of a different magnitude — COPPA, state-level child privacy laws, potential FTC action. Paying the ransom and announcing you got confirmation of destruction may actually create additional liability if it turns out that data surfaces later, because you've made a representation to victims that you cannot substantiate. CISOs should make sure their legal counsel and board understand this dynamic before a crisis, not during one.

Jordan: Let's shift to the geopolitical layer. Pentagon cyber official Paul Lyons characterized advanced AI as "revolutionary warfare" this week. He emphasized offensive cyber alongside AI in the same framing. This is DoD signaling, and DoD signaling has downstream consequences.

Alex: It does. And for CISOs in the defense industrial base or critical infrastructure, that framing has very practical implications. When the Pentagon describes something as revolutionary warfare, that language eventually becomes policy, which becomes compliance mandates, which becomes contract requirements. If you're working toward CMMC or you have DoD contracts, the AI security posture expectations are moving targets and they're moving fast.

Jordan: Relatedly, Mustang Panda — the Chinese state-sponsored group — has a new modular backdoor in circulation called FDMTP, deployed in a cyberespionage campaign targeting Asia-Pacific government organizations. Modular architecture means they're building for persistence and adaptability. Detection rules written against their older tooling won't catch this cleanly.

Alex: If you have APAC operations, government clients, or you sit in any supply chain adjacent to regional governments in that theater, update your threat models. The sophistication trend in Chinese state-sponsored tooling is not plateauing.

Jordan: Quick note on the market side. Akamai is acquiring LayerX for $205 million. LayerX does enterprise browser security — AI usage controls, visibility into what employees are doing with generative AI at the browser layer, SaaS exposure management. Akamai is folding it into its zero trust portfolio.

Alex: The signal here for security architects is that browser-level visibility is graduating from "niche product" to "mainstream zero trust requirement." If you don't have insight into what's leaving your environment through the browser — AI prompts, SaaS uploads, OAuth grants — that's a gap worth evaluating in your next architecture review.

Jordan: And briefly, the EY survey finding that CISOs are increasingly owning physical security budgets is worth flagging for anyone in that position. If you're being handed scope, make sure you're also being handed headcount and budget. Don't let expanded responsibility become a liability without resources.

Alex: Looking at the week as a whole, the theme I keep coming back to is the compounding complexity of the attack surface. You have developer toolchains, manufacturing supply chains, browser-layer AI exposure, SD-WAN infrastructure, on-prem email servers — all of it active this week. The adversaries are not specializing. They're opportunistic across all of it.

Jordan: And the AI framing from the Pentagon is relevant even for non-defense CISOs because it signals what the threat environment is heading toward. When nation-state actors start integrating advanced AI into offensive operations at scale, the velocity of attacks changes. The window between vulnerability disclosure and exploitation, already compressed, compresses further.

Alex: The action items for this week are concrete. Patch CVE-2026-20182 immediately if you're running Cisco SD-WAN. Apply Microsoft's temporary mitigations for CVE-2026-42897 on any on-prem Exchange deployment. Assess your Foxconn exposure and know your contractual notification obligations. Audit your developer dependency pipelines. And if you don't have a board-approved ransom payment policy that accounts for data belonging to minors, put it on the agenda before you need it.

Jordan: Have a good weekend. Or what's left of it.

Alex: Thanks for listening to Cleartext. Show notes and links to every story we covered today are at cleartext.fm. We'll be back Monday.