CNIL Fines French Hospital EUR 500,000 Over Breach Notification Failure

CNIL Fines French Hospital EUR 500,000 After Breach Hit Patients and Their Emergency Contacts

France's data protection regulator fined Hôpital Privé de la Loire EUR 500,000 on a decision published September 3, 2026, over a summer 2025 attack that exposed data on 524,867 patients and 202,246 people those patients had named as trusted contacts. The hospital told the patients. It never told the contacts.

Information last verified on September 3, 2026. This is a developing story; we update it as the record changes.

Status: Final sanction issued by the CNIL's formation restreinte, the body inside the regulator that decides penalties. The CNIL published the decision on September 3, 2026; the deliberation itself is numbered SAN-2026-009 and dated July 21, 2026. Recording Law did not confirm whether the hospital has challenged the decision before the Conseil d'État, and the CNIL's announcement does not say.

Jurisdiction scope: This article covers a French regulatory decision applying the EU General Data Protection Regulation. It does not address US state or federal health-privacy law, which works differently. Readers looking for the US rules on medical records should start with our separate American coverage rather than assume this decision transfers.

What Happened

The Commission nationale de l'informatique et des libertés, France's data protection authority, announced on September 3, 2026 that it had fined Hôpital Privé de la Loire EUR 500,000. The penalty was imposed by the formation restreinte, the CNIL body responsible for sanctions, in deliberation number SAN-2026-009, which the regulator's published reference dates July 21, 2026.

The underlying incident happened in the summer of 2025. An attacker managed to log in to the hospital's dossier patient informatisé, the computerised patient record system that centralises data on everyone the hospital treats. From there the attacker reached the records of 524,867 patients, health data among them for some, and of 202,246 further people whom patients had designated as "tiers de confiance", trusted third parties. Those two groups together come to more than 727,000 people affected by a single intrusion.

Following the breach, the CNIL carried out an inspection, and that inspection produced the findings the fine rests on. The regulator's announcement does not say how the CNIL came to learn of the incident.

The security failures

The regulator identified three specific gaps, and it framed them as elementary measures whose absence made the attack easier rather than as exotic oversights.

First, the authentication used by people connecting to the patient record system from outside the hospital, the CNIL singles out independent doctors among them, was not robust enough, because there was neither a VPN nor any multi-factor authentication. That is the weakness the attacker exploited to get in.

Second, the hospital's authorisation policy was inadequate. It did not build in the notion of the care team, the arrangement under which only the professionals actually involved in treating a given patient can see information covered by medical confidentiality. Because access was not limited that way, the attacker holding the credentials of one single user account could reach the data of the hospital's entire patient population.

Third, the hospital had taken no measures capable of detecting suspicious activity inside the record system in real time or over a very short horizon, and of raising an alert when it appeared. The consequence, in the CNIL's account, is that the attacker was able to explore the system for several days and extract a very large volume of data without that abnormal activity being spotted. The regulator treated this as having made the breach worse than it needed to be.

The formation restreinte noted that the hospital had taken several steps during the proceedings to raise its security level, and it required the hospital to finish implementing them within deadlines ranging from three to fifteen months depending on the type of measure. It also restated a point worth keeping in view: while no organisation can eliminate risk entirely, appropriate security measures can reduce both the probability and the severity of an incident.

The notification failure

The second finding is the one that makes this decision worth reading beyond France, and it is the part most coverage of hospital breaches skips.

Under Article 34 of the GDPR, a controller must communicate a personal data breach to the data subjects affected by it when the breach is likely to result in a high risk to their rights and freedoms. The CNIL found that only the hospital's patients had been informed. No direct information was given to the 202,246 people designated as trusted third parties, even though the attacker had stolen their personal data too.

The regulator explained why that omission mattered in concrete terms rather than formal ones. Not telling those people deprived them of the information they needed to understand the nature of the attack and its likely consequences, and to know what steps would limit those consequences and guard against possible malicious use of their data.

What the Law Actually Says

Two separate GDPR obligations are in play here, and the decision is a clean illustration that they fail independently of each other.

Article 32 requires a controller to implement technical and organisational measures appropriate to the risk. The CNIL's application of it here is unremarkable in principle and instructive in detail: the measures it faulted, remote-access authentication, role-scoped permissions, and monitoring capable of catching an intruder in progress, are baseline controls rather than advanced ones, and the regulator weighed the number of people and the nature of the data in judging what was appropriate. Health data raises that bar.

Article 34 is the duty to communicate a breach to the individuals affected. It is distinct from the separate duty to notify the supervisory authority, which our guide to the GDPR's 72-hour breach notification rule covers, and it runs to data subjects rather than to customers. That distinction is the whole of the second finding. A trusted contact named by a patient is not a patient, has no treatment relationship with the hospital and may never have interacted with it at all, but once that person's data sits in the hospital's system and is stolen, they are a data subject affected by the breach and the Article 34 duty reaches them.

For readers following how French data protection works in practice, our overview of GDPR enforcement in France sets out the CNIL's powers, and our guide to taking a complaint to the CNIL covers the route an individual takes. The fine also sits in a wider enforcement picture we track on our page covering GDPR fines and their current status.

Analysis: Why This Matters

The following is analysis from the Recording Law Editorial Team.

The security findings are familiar. A hospital without multi-factor authentication on external access, without permissions scoped to the care team, and without meaningful monitoring presents what reads to us as a familiar enforcement profile, and nothing in the CNIL's reasoning on Article 32 announces a new standard.

The notification finding is different, and it is the reason this decision deserves attention outside France. Most breach-response planning is organised around a customer list. The hospital appears to have done what such a plan would produce: identify the patients, tell the patients. The CNIL's holding is that this was not enough, because the population whose data was taken was larger than the population the hospital had a relationship with. Systems that let one person name another, an emergency contact, a next of kin, a designated support person, quietly accumulate personal data about people who never signed up for anything, and Article 34 does not distinguish between them and the account holder.

That is a structural problem rather than a French one. The same shape appears in any system holding beneficiary details, guarantor records, referral contacts or dependants. An organisation that maps its notification duty to its customer database, rather than to the data subjects actually present in the breached system, can satisfy itself that it has notified everyone while leaving a large group uninformed. Here that group was just over a quarter of the people affected, 202,246 of 727,113.

It is also worth noting what the CNIL said about the monitoring gap, because it went to scale rather than to entry. The absence of VPN and multi-factor authentication explains how the attacker got in; the absence of detection explains why the intrusion produced 727,000 affected people instead of a smaller number. The regulator treated the second as an aggravating contribution to the breach's extent, which is a useful reminder that detection controls carry weight in an enforcement analysis and not only prevention controls.

We are not predicting whether the hospital will challenge the decision or how any challenge would be resolved.

How This Affects You

If you are in France and were treated at this hospital, or were named by a patient as a trusted contact, the CNIL's decision is a regulatory finding against the hospital rather than a compensation process, and it does not itself award anything to individuals. The GDPR separately allows individuals to seek compensation for damage through the courts, which is a different route from a regulatory complaint.

More generally, this decision is a reminder that the people affected by a health-sector breach are not always the people on the patient list. Anyone who has ever been named as someone else's emergency or trusted contact has personal data sitting in systems they have no relationship with, and will not necessarily hear about it if those systems are breached.

For organisations, the transferable point is narrow and checkable: the question is not who your customers are, it is whose personal data was in the system that was breached. This article describes general legal principles and a specific regulatory decision; it is not advice on any organisation's or individual's particular situation.

This is general legal information, not legal advice. It describes a French regulatory decision under the EU General Data Protection Regulation, verified against the CNIL's own published announcement on September 3, 2026. It does not cover US health-privacy law. Laws and enforcement positions change; consult a lawyer qualified in the relevant jurisdiction about your specific situation.

Related articles

• How GDPR enforcement works in France
• Taking a complaint to the CNIL
• The GDPR's 72-hour breach notification rule
• The largest GDPR fines and where they stand
• Ireland's DPC fined the HSE over medical records left to rot

---

Last updated: 2026-09-03. This is a developing story; details verified as of 2026-09-03.

Frequently Asked Questions

How much did the CNIL fine Hôpital Privé de la Loire?

EUR 500,000. The CNIL published the decision on September 3, 2026; the deliberation, numbered SAN-2026-009, is dated July 21, 2026 in the regulator's own reference to it.

How many people were affected by the breach?

The attacker reached data on 524,867 patients, including health data for some of them, and on 202,246 people whom patients had designated as trusted third parties, more than 727,000 people in total.

What security failures did the CNIL identify?

Three. Remote access to the patient record system lacked both a VPN and multi-factor authentication; the authorisation policy did not restrict access to the care team, so one compromised account could reach every patient's records; and there was no capability to detect suspicious activity in real time, so the attacker explored the system for several days undetected.

Why was the hospital penalised over notification when it did tell patients?

Because GDPR Article 34 runs to everyone affected by the breach, not only to the organisation's own patients or customers. The CNIL found the hospital gave no direct information to the 202,246 designated trusted third parties whose data was also stolen.

What is a 'tiers de confiance' in this decision?

The CNIL describes them as people designated by patients as trusted third parties. Their personal data was held in the hospital's patient record system and was taken in the same intrusion, which is what brought them within the notification duty.

Does GDPR Article 34 apply to people who were never customers?

The duty is owed to data subjects affected by the breach. This decision applies it to individuals whose data was in the breached system because someone else named them, rather than because they had a relationship with the controller.

What is the difference between Article 33 and Article 34 of the GDPR?

Article 33 concerns notifying the supervisory authority about a breach; Article 34 concerns communicating it to the affected individuals. They are separate obligations and an organisation can comply with one and not the other. The CNIL's findings in this case were under Articles 32 and 34.

Does the fine mean affected people get compensation?

No. A CNIL fine is a regulatory penalty paid to the state, not a compensation fund. The GDPR provides a separate route for individuals to seek compensation for damage through the courts.

What must the hospital do now besides pay?

The CNIL noted the hospital had already taken several measures to strengthen its security during the proceedings, and required it to finish implementing them within deadlines of between three and fifteen months depending on the type of measure.