Ivanti has released fixes for two vulnerabilities, CVE-2026-111357 and CVE-2026-118527, which were exploited together with an earlier authentication-bypass flaw, CVE-2026-104935, to chain to elevated privileges on Connect Secure VPN appliances. The US Cybersecurity and Infrastructure Security Agency (CISA) added the flaws to its Known Exploited Vulnerabilities catalog, with an urgent November 2 remediation deadline for one of them. The details are technical, but the business lesson is plain: for enterprise-facing founders, patch cadence and compromise assessment are product features, not support chores.
What chaining means, in plain language
A single vulnerability is often described as if it were the whole attack. In this case, the attack worked by chaining flaws together. An earlier authentication bypass — a way to get past a login check that should have stopped an unauthorised user — combined with the newer flaws to reach elevated privileges on the VPN appliance. Elevated privileges mean the attacker gains more control than an ordinary user should have, potentially enough to persist, move within a network, or alter the device.
VPN appliances sit at the boundary of an organisation's network, are reachable from the internet by design, and often provide access to internal systems once a session is established — so compromising one can be a foothold into the network behind it. CISA catalog inclusion signals observed exploitation and urgent remediation, not a theoretical risk.
Two hard truths: earlier patches do not cover later flaws, and patching does not remove persistence
Two facts from this incident deserve emphasis because founders and buyers often misunderstand them.
First, an earlier patch does not cover later flaws. Organisations that patched CVE-2026-104935 may have assumed they were protected, only to find that the newer vulnerabilities opened a different path to the same outcome. Security is not a one-time fix. Each new flaw can create a new chain, even if the old chain is closed.
Second, patching does not remove already-established persistence. If an attacker has already gained a foothold — for example, by installing a backdoor, creating a hidden account, or altering configuration — applying a patch closes the entry point but does not necessarily evict the intruder. The intruder may already be inside, using a different mechanism. That is why incident guidance for exploited VPN flaws typically pairs patching with a compromise assessment: checking logs, configurations, accounts, and network activity for signs that the device was already abused.
Founders who sell into enterprises must internalise both truths. A customer who asks "are we patched?" is asking an incomplete question. The complete questions are: "Are we patched against all known chained flaws? Have we checked whether we were compromised before patching? And can we prove it?"
Why VPN appliances keep getting targeted
VPN appliances are high-value targets for structural reasons, not just because of any single vendor's code. They are internet-facing, they handle authentication, they often run with high privileges, and they are frequently managed as infrastructure rather than as applications — meaning updates can lag, monitoring can be thin, and ownership can be split between networking and security teams.
For a founder, that structure is both a warning — any internet-facing infrastructure product will be attacked this way — and an opportunity: enterprises will pay for products that make secure operation easier.
What this means for founders selling into enterprise
If your product will sit in an enterprise network, on an enterprise device, or in front of enterprise data, treat patch cadence and compromise assessment as features to design, demo, and document — not as items to handle after a sale.
In practice, that means several things. Ship updates that are easy to apply without breaking the customer's operations, and be explicit about downtime, rollback, and testing. Provide a clear, dated record of which versions fix which flaws, so a security team can verify coverage without guessing. Build logging and health checks that make compromise visible, rather than assuming a patched system is a clean system. And when a vulnerability is exploited in the wild, communicate quickly and concretely: what is affected, what to patch, what to check, and what to do if compromise is found.
What investors should ask
For investors, diligence operational security, not just product security: how quickly can the team ship and verify a fix, what fraction of customers are on patchable versions, and how would it know if a customer was already compromised? A startup that treats patching as someone else's problem carries hidden risk that surfaces during a security review or after an incident.
The bottom line
The Ivanti VPN flaws are a case study in patch debt: the gap between knowing a fix exists and having it applied, verified, and checked for prior compromise across every exposed device. Closing that gap is unglamorous work. It is also, for founders selling into enterprise, one of the most valuable things a product can do.
Angeled.com connects founders with investors.
Read Next
What a Reported $15B Raise at a $1.25T Valuation Would Mean for OpenAI — and Everyone Else
AlphaGenome 2 and the New Tooling Layer for Biotech Founders
Big Law Is Now Paying Lawyers to Learn AI — and That Changes Legal Tech
Biotech's $348 Million Week: Brain Drugs, Radiopharma and Gene Therapy
Databricks' Always-On Genie and the End of the Chatbot Era
Gemini Decision 1: Google's AI That Answers Instead of Chatting



