Opens in a new tab

KPMG Canada Breach Exposes Client Tax Files

KPMG Canada confirms data breach exposing client files

The KPMG Canada breach has compromised client tax documents, prompting the professional services firm to contact affected clients. The incident was made public on 18 November 2026, but its scale and technical cause remain undisclosed.

KPMG Canada breach: What happened

KPMG Canada confirmed that some client files had been compromised in a data breach. The affected material was described as tax documents, which can contain commercially and personally sensitive information supplied for tax preparation, compliance and advisory work.

The firm is contacting clients whose documents were affected. However, it has not disclosed how many clients received notifications, how many files were compromised, or whether the incident affected particular offices, business units or types of engagement.

KPMG also said that its ongoing monitoring had found no evidence that the impacted information was available online or being misused. This is an important current status update, but it does not establish that the information was never copied, viewed or retained by an unauthorised party.

The KPMG Canada breach is a confirmed compromise rather than an unverified claim. However, the information available publicly is limited. There was no public incident notice in the KPMG Canada newsroom at the time of reporting, so clients and other interested organisations have not yet received a detailed technical account through that channel.

What information was compromised

Public reporting identifies the affected files as client tax documents. It does not describe the individual data fields within those documents, the relevant tax periods, or whether corporate and personal records were both involved.

Tax documents may vary considerably between clients. Consequently, organisations should not assume that every affected file contained the same categories or volume of information. Direct notification from KPMG will be central to understanding the actual exposure in each case.

No specific software product, service version or configuration has been linked to the KPMG Canada breach. This is not a published vulnerability for which organisations can apply a patch, and no affected product versions have been identified.

Timeline and current status of the KPMG Canada breach

The first public report identified in available coverage was published on 18 November 2026. It stated that KPMG Canada had confirmed the compromise of client files, while declining to specify the number affected.

Further reports on 18 November 2026 said the firm was contacting clients whose tax documents had been compromised. These reports repeated that neither the affected client count nor the method used to gain access had been disclosed.

As of 18 November 2026, the following points were established:

  • KPMG Canada had confirmed that some client tax documents were compromised.
  • The firm was contacting affected clients directly.
  • No number of affected clients, documents or records had been published.
  • No threat actor had been publicly identified.
  • No initial access method, malware family or exploited vulnerability had been disclosed.
  • KPMG’s monitoring had not identified the affected information online or being misused.

The date on which the underlying intrusion began is not public. There is also no disclosed information about how long access persisted, when KPMG detected the activity, when the attacker was removed, or when remediation was completed.

These gaps make it impossible to construct a detailed incident timeline or assess dwell time from the public record. They also mean that any claim attributing the KPMG Canada breach to a particular group, campaign or vulnerability should be treated cautiously unless KPMG or an investigating authority provides confirmation.

How the compromise occurred remains unknown

KPMG has not publicly explained how access to the client files was obtained. There is no confirmed information about phishing, stolen credentials, compromised remote access, exploitation of an internet-facing system, insider activity, or an attack involving a third-party platform.

The affected infrastructure has not been identified either. Public reporting does not say whether the tax files were held in email, document management systems, collaboration platforms, cloud storage, client portals, local servers or another environment.

No indicators of compromise have been released. Organisations therefore do not have incident-specific internet addresses, domains, file hashes or detection rules that could be used to search their own environments for activity connected with this event.

There is also no proof of concept or patching instruction associated with the case. Those concepts apply to disclosed vulnerabilities, whereas the KPMG Canada breach is currently described only as an incident involving compromised documents.

No public evidence of data misuse

KPMG’s statement that monitoring had not found the information online or being misused provides some reassurance. It indicates that the firm had not observed public publication or known exploitation of the documents at the time of its statement.

However, monitoring results can change as an investigation develops. Information may also be used privately for fraud, impersonation or targeted approaches without appearing on a public leak site. Affected clients should therefore rely on direct updates and any individual risk assessment provided during notification.

Separate, unverified ransomware claims mentioning KPMG appeared online in January 2026. Those claims were not confirmed and should not be presented as connected to this November incident. No public evidence currently establishes such a link.

Why the KPMG Canada breach matters to UK organisations

There is no indication in the available reporting that KPMG UK or UK client files were affected. The confirmed scope concerns KPMG Canada and client tax documents handled within the affected environment.

Nevertheless, UK organisations using KPMG may need to establish whether their information is processed by Canadian teams, transferred across jurisdictions, or stored in systems shared with Canadian operations. This is a targeted supplier risk question, not evidence that all KPMG clients are exposed.

Tax files can support convincing impersonation attempts because they may provide context about an organisation, its personnel or financial affairs. Any organisation receiving an incident notification should alert relevant finance, tax, legal and security contacts so that suspicious requests can be assessed against the known exposure.

Actions for clients and supplier risk teams

Organisations contacted about the KPMG Canada breach should request a written account of the files and data categories involved. They should also establish the relevant tax periods, affected individuals or entities, known access activity, containment status and planned notification schedule.

Practical event-specific actions include:

  • Confirm whether organisational data was handled by KPMG Canada or accessible through affected systems.
  • Verify any notification through established KPMG contacts rather than replying to an unexpected message.
  • Record the incident in the supplier risk register and preserve related correspondence.
  • Review unusual tax, payment or identity verification requests that use information connected with the affected documents.
  • Confirm internal escalation routes for privacy, contractual and regulatory assessment if exposure is verified.

Because no vulnerable product or intrusion route has been identified, broad claims about required patches would be premature. The immediate priority is accurate scoping through KPMG’s client outreach, followed by proportionate monitoring based on the specific documents confirmed as compromised.

Originally reported by The Globe and Mail.

Share this bulletin

About the Author

Headshot of Jonny Pelter, leading cyber security expert in the UK and CISO

Jonny Pelter

Partner

  • CIPM
  • CIPP/E
  • CISSP
  • CISM
  • CRISC
  • ISO27001
  • Prince2
  • MSc
  • BSc

Jonny Pelter

Jonny is a Founding Partner at CyPro and executive group level CISO who has worked closely with the British intelligence agencies NCSC and GCHQ.

An ex-professional rugby player and originating from KPMG and Deloitte, Jonny has a wealth of experience across numerous sectors including technology, critical national infrastructure, financial services, oil & gas, insurance, betting, pharmaceuticals and utilities.

Jonny is a leading cyber security expert in the UK, having featured on national media for his professional commentary such as BBC News, iPlayer, Telegraph and Times Radio.

View Profile
Back to Bulletins

Related CyPro Services

  • Managed Detection and Response (MDR)

    Managed Detection and Response (MDR) is an end-to-end managed service designed to help organisations detect, analyse and respond to cyber threats quickly and effectively. It...
    View Service
CyPro Cookie Consent

Hmmm cookies...

Our delicious cookies make your experience smooth and secure.

Privacy PolicyOkay, got it!

We use cookies to enhance your experience, analyse site traffic, and for marketing purposes. For more information on how we handle your personal data, please see our Privacy Policy.

Schedule a Call