Threat intel
A La Poste subsidiary breach exposed 22 million people
Maileva, a business-mail service owned by Docaposte and La Poste, lost names and postal addresses for 22 million people. What happened, and what processor breaches mean for you.
La Poste, the French postal group, confirmed to the news agency AFP on 14 November 2026 that one of its services lost the personal data of about 22 million people. The service is Maileva, a business-mail platform run by Docaposte, La Poste's digital subsidiary. Companies use Maileva to print and send letters, registered mail, payslips and invoices on their behalf, so the 22 million are mostly people who received such mail, not people who ever signed up with Maileva themselves.
The stolen data is limited to identification details: first name, last name and postal address. That makes it less dangerous than a leak of passwords or bank details, but it is still one of the largest breaches reported in France, and the people affected have no direct relationship with the company that lost their data. That gap, between who gets breached and whose data is in the breach, is the part worth your attention.
What Maileva is, and how it holds your data
Maileva is a registered and hybrid-mail service. A business uploads a document and a recipient list; Maileva prints and posts the letters, or sends them digitally. La Poste says the platform has more than 70,000 users and sent 180 million documents in 2024. Its clients span social housing landlords, health and diagnostic labs, hospitals and public services, which is why the recipient lists read like a cross-section of the French population.
The chain of custody is what matters here. A tenant gives their address to their landlord. The landlord hands a mailing to Maileva. Maileva is owned by Docaposte, which is owned by La Poste. So a single person's address can sit in the production systems of a company three steps removed from the one they actually dealt with. When that third party is breached, every recipient in every client's list is exposed at once, which is how a single intrusion reaches 22 million people.
The 22 million is a deduplicated count. Cyberattaque.org, the French breach-tracking outlet that first reported the figure and to which Maileva confirmed it, says internal Docaposte documents held roughly 39 million mail references. One person often receives several letters, so the references collapse to about 22 million distinct individuals once duplicates are removed. The 22 million headcount is what La Poste confirmed to AFP; the 39 million mail references are a single-source detail from Cyberattaque.org citing internal documents.
What was taken, and what was not
For most people, the exposure is first name, last name and postal address. That is the common set across all affected organisations, and the only set Maileva itself named. It is contact data, not credentials or payment data.
Some client organisations held more, and said so. Affected bodies reported additional fields depending on their mailings: email addresses, internal identifiers, document or file names, and for some, invoice amounts or dates of care. The diagnostic-lab group Inovie stated that payment data and passwords were not affected. The transport network IZILO stated that bank details were not affected. No source reports that passwords, card numbers or bank details were in the breach, and no attacker has published a sample or claimed responsibility.
The practical risk from name-and-address data is targeted fraud by post and by phishing. Someone who knows your name, your address and which hospital, lab or landlord sent you mail can write a convincing fake letter: a forged change-of-bank-details notice, a fake invoice, a payment demand that cites a real care date. It works because the details check out. Anyone affected should treat unexpected letters or emails about payments or account changes with suspicion and verify through a known channel before acting.
The timeline, and what is still unknown
The attack happened in mid-September 2026. Maileva detected unauthorised access attempts and suspended all its services on 23 September at 07:00 as a precaution, which cut off its clients' sending channel for six days. Docaposte restored the platform on 29 September. The data theft stayed quiet until 14 November, when Cyberattaque.org reported it and La Poste confirmed the 22 million figure to AFP, nearly two months after the intrusion was discovered.
How the attacker got in has not been publicly confirmed. La Poste says a judicial investigation is open to establish the entry point, and early coverage listed stolen credentials, a missing second authentication factor or a platform flaw as possibilities without settling on one. Maileva notified the CNIL, France's data protection regulator (the Commission Nationale de l'Informatique et des Libertes), and filed a criminal complaint. Under European data protection rules, Maileva informed the affected client companies, and each of those companies is responsible for notifying the individuals on its own lists, which is why no single total exists for how many people have actually been told.
What organisations should take from this
The lesson is not about one French mail platform. It is that your customers' data lives in places you do not run, and a breach there is still your breach to notify and explain.
- Map where customer data actually goes. List every processor, subsidiary and sub-processor that handles personal data on your behalf: the mail house, the billing platform, the analytics vendor, the group company you route data through. A tenant whose address leaked through Maileva never chose Maileva; the landlord did. You are accountable for the parties you chose.
- Put breach-notification duties in the contract. Require each processor to notify you of a suspected breach within a fixed, short window, with the categories of data and the number of records involved, so you are not learning the scope from a news outlet weeks later. This is also what the European General Data Protection Regulation (GDPR) expects of the processor relationship.
- Test the applications that face production data. The systems that reach live personal data, and especially any portal or interface exposed to clients or the internet, are the ones an external attacker reaches first. A web application penetration test looks for exactly the weaknesses that let an outsider cross from a login page into a production database.
- Know what you cannot see from inside. Most organisations cannot list, from memory, every system of theirs that is reachable from the internet, let alone every system of every processor. Attack surface management is the work of building and keeping that list current, because the asset you forgot is the one that gets hit.
- Prepare the GDPR notifications before you need them. Under GDPR, a data controller must report a qualifying personal-data breach to its supervisory authority (the CNIL in France) within 72 hours under Article 33, and must tell the affected individuals without undue delay under Article 34 when the breach is likely to be a high risk to them. Have the templates, the contacts and the decision criteria ready now, not during the incident.
Maileva did notify the regulator and file a complaint, which is the correct path. The weeks between the September intrusion and the November public confirmation are the reminder: a processor breach can sit quiet while your name is on the data. If you are not sure which third parties and subsidiaries hold your customers' details, or whether the apps that touch that data would survive an external attacker, open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.
Sources: Franceinfo with AFP, 14 November 2026, CNEWS, Univers Freebox, Cyberattaque.org, Solutions Numeriques on the September outage, CNIL on breach notification (GDPR Articles 33 and 34).