Skip to main content

The Cyber Attacks of 2025 and 2026, and Why Self-Hosted Software Matters Again

From the Canvas and Klue breaches to the Canadian law firm hacks and the Bell incident, a look at the biggest recent cyber attacks and when self-hosted software gives your business more control over its own risk.

Bytesavy9 min read

Short answer: the biggest data breaches of 2025 and 2026 mostly came through shared platforms. Attackers compromised one software-as-a-service (SaaS) vendor, one integration or one cloud login, and reached thousands of organizations at once. Self-hosted software, running on infrastructure you control, reduces that shared exposure and keeps your data under your own policies and in your own jurisdiction. It is not automatically safer: several of the worst mass exploitations of the same period hit self-hosted servers that were not patched quickly. The right answer for most organizations is to self-host the systems and data that matter most, harden them properly, and be deliberate about every third party that can touch them.

What were the most significant cyber attacks of 2025 and 2026?

WhenIncidentHow it happenedType
Nov 2026Bell CanadaAn attacker Bell described as "agentic" accessed a system used to order and provision business circuits and took business contact informationProvider system
Oct 2026Canadian law firms (McCarthy Tétrault, Davies, Bennett Jones, BLG)Voice phishing over Microsoft Teams and phone sent staff to fake sign-in pages that bypassed multifactor authentication; about 31,000 files were taken from one firmCloud identity
Jul to Sep 2026Ontario courtsUnauthorized activity on a third-party case-management platform used by the courtsThird-party platform
Jul 2026Microsoft SharePoint Server (CVE-2026-58644)A critical remote code execution flaw in on-premises SharePoint, patched July 14 and added to CISA's list of exploited vulnerabilities two days laterSelf-hosted
Jun 2026KlueA credential issued in 2022 for a pilot was never revoked; attackers used it to steal OAuth tokens and download customers' data from other clouds, with LastPass among those affectedSaaS integration
May 2026Instructure CanvasShinyHunters claimed data on about 231 million people across almost 9,000 schools, then defaced school login pagesSaaS
Mar 2026LoblawCustomer data for about 2 million Canadians accessed through the company's IT networkUndisclosed
Nov 2025PowerSchool findingsOntario and Alberta privacy commissioners reported on the breach of the student information platform used by school boardsSaaS
Oct 2025AWS us-east-1 outageNot an attack: a fault in automated DNS management caused a roughly 15 hour disruption that cascaded across many servicesCloud concentration
Sep 2025Collins Aerospace MUSERansomware on a shared check-in and boarding platform disrupted airports across EuropeShared vendor platform
Sep 2025Cisco firewalls (CISA ED 25-03)Exploited flaws in Cisco ASA and Firepower devices led to an emergency directiveSelf-hosted appliance
Aug to Sep 2025Salesloft DriftStolen OAuth tokens from one integration were used to pull data from many companies' Salesforce instancesSaaS supply chain
Aug to Sep 2025Oracle E-Business SuiteA zero-day in self-hosted Oracle EBS was exploited and followed by Cl0p extortion emailsSelf-hosted
Jul 2025SharePoint "ToolShell" (CVE-2025-53770)Mass exploitation of on-premises SharePoint Server breached hundreds of organizationsSelf-hosted
2025Nova Scotia PowerCustomer data stolen and operations disrupted for monthsUndisclosed

Sources are linked throughout the sections below.

What do these attacks have in common?

One vendor, thousands of victims

The pattern that defined 2026 was concentration. When Instructure's Canvas was breached, every school on the platform was exposed at once, including Canadian universities such as the University of Toronto, OCAD and UBC according to Radio-Canada. The same was true of PowerSchool, where the privacy commissioners also criticized weak contract terms and vendor oversight. None of the affected institutions made a mistake on the day. Their exposure came from sharing a platform with everyone else.

Integrations are the new front door

The Salesloft Drift and Klue incidents did not break into Salesforce or the clouds themselves. Attackers stole the OAuth tokens that small, connected tools held, and those tokens opened customers' data in other systems. In Klue's case, the credential had sat unused since a 2022 pilot. Every app you connect to your core systems becomes part of your attack surface.

Identity is the target

The Canadian law firm breaches began with phone calls and Teams messages from people pretending to be IT staff. Once an attacker controls a cloud login, everything that login can reach is exposed, from anywhere in the world.

Self-hosted servers are targets too

The other half of the story is less comfortable for self-hosting advocates. On-premises SharePoint was mass exploited in 2025, and again in 2026. Oracle E-Business Suite and Cisco firewalls followed. Organizations that ran these systems themselves and patched slowly paid the price.

Concentration also means outages

The October 2025 AWS outage was not an attack, but it showed the same risk from a different angle: when one region of one provider fails, a large share of the internet fails with it. The Collins Aerospace ransomware attack showed what happens when many organizations depend on one shared operational platform.

Why does self-hosted software matter again?

You stop sharing someone else's blast radius

When your system runs in your own environment, an attacker who breaches a popular SaaS vendor does not get your data along with everyone else's. You are no longer a bonus prize in an attack aimed at thousands.

You control who and what can connect

Self-hosted software lets you decide exactly which integrations exist, which tokens are issued and when they expire. Nothing is connected because a vendor enabled it by default.

Your data stays in your jurisdiction

Canadian organizations increasingly want their data stored in Canada and governed by Canadian law. The federal government's Responsible Data Centre Development Principles, released in September 2026, state plainly that Canada "relies significantly on infrastructure and services based outside the country" for compute, cloud and data storage. Self-hosting in a Canadian facility, or on Canadian-owned infrastructure, removes the question entirely.

You keep working when a provider goes down

A system on your own infrastructure does not stop because a cloud region or a SaaS vendor has a bad day. For operations that must keep running, such as utilities, clinics, plants and field crews, that independence is worth a lot.

You own the logs and the evidence

When something goes wrong, you have the full record of what happened, not just what a vendor chooses to share, and you can respond on your own timeline.

What are the trade-offs of self-hosting?

Self-hosting moves responsibility to you. Be honest about what that means:

  • Patching is your job. The SharePoint, Oracle and Cisco incidents show that unpatched self-hosted systems are prime targets. You need a process to apply critical updates within days, not months.
  • You need monitoring. Someone must watch logs, alerts and unusual activity.
  • Backups must be real. Offline or immutable backups, tested regularly, are what let you recover from ransomware.
  • Expertise costs money. Running servers securely takes skill, whether in-house or from a partner.
  • Identity still matters. A self-hosted system with weak sign-in protection can still be reached by phishing.

Should everything be self-hosted?

No. For most organizations, a hybrid approach is the strongest position:

  • Self-host the systems that hold your most sensitive data or run your core operations: client records, case files, health information, financial systems, proprietary data and the software that makes your business different.
  • Use trusted cloud services for commodity functions such as email, where large providers invest more in security than most organizations can.
  • Minimize integrations between the two, and give each one the least access it needs, with tokens that expire.

How do you self-host safely?

  1. Keep internet exposure small. Put administrative interfaces behind a VPN or zero-trust access, never on the open internet.
  2. Use phishing-resistant multifactor authentication, such as security keys or passkeys, for every account that can reach sensitive systems.
  3. Patch on a schedule and on demand. Track vendor advisories and the CISA Known Exploited Vulnerabilities catalogue, and patch critical issues immediately.
  4. Segment the network so one compromised machine cannot reach everything.
  5. Encrypt data at rest and in transit.
  6. Keep offline, tested backups and practise restoring them.
  7. Log centrally and review alerts, with someone accountable for responding.
  8. Revoke what you no longer use: old accounts, test credentials and integration tokens. The Klue breach started with a credential that should have been deleted years earlier.
  9. Build on open, portable technology such as Postgres, containers and standard APIs, so you can move between your own servers and a cloud provider if needs change.

Frequently asked questions

Is self-hosted software more secure than the cloud?

Not automatically. Self-hosting removes shared-platform risk and gives you control, but it makes you responsible for patching, monitoring and backups. A well-run self-hosted system is very secure; a neglected one is an easy target.

What is the difference between self-hosted and on-premises?

On-premises means the servers are physically in your building. Self-hosted is broader: you run and control the software yourself, whether on your own hardware, in a colocation facility or on servers you manage at a Canadian hosting provider.

Does self-hosting help with Canadian privacy law?

It makes data residency and control simpler to demonstrate, which helps with PIPEDA, Quebec's Law 25 and provincial health privacy laws. See our guide to building software that meets Canadian privacy law.

Can we move an existing SaaS system to self-hosted software?

Often, yes. Many organizations replace a SaaS tool with custom software they own, migrating data in stages. Read how to modernize a legacy system without stopping the business.

What does self-hosting cost compared with SaaS?

There is more upfront work and you take on operating costs, but you stop paying per-user subscription fees and you own the result. Compare the five-year total, including the cost of a breach. Our guide to how much custom software costs explains what to budget for.

Build software you control

Bytesavy builds custom software that can run on your own servers, in a Canadian data centre or in the cloud account you choose, with security designed in from the start. We help organizations decide which systems to bring in-house, migrate them safely and keep them patched and monitored after launch. Explore our custom software development and cloud and infrastructure services, or book a scoping call.

Facing a challenge like this one?

We design, build and modernize the systems essential industries run on. Tell us what you are working on.

Book a scoping call

A reply within one business day. No obligation.

Prefer email? sales@bytesavy.com