<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Gdpr | FirewallSync</title><link>https://firewallsync.com/tags/gdpr/</link><description>Practical cybersecurity writing for engineering teams that ship fast.</description><language>en-us</language><image><url>https://firewallsync.com/icon-512.png</url><title>FirewallSync</title><link>https://firewallsync.com/</link></image><lastBuildDate>Mon, 16 Nov 2026 04:58:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/gdpr/index.xml" rel="self" type="application/rss+xml"/><item><title>Maileva Data Breach: La Poste Says 22 Million Hit</title><link>https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/</link><guid>https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/</guid><pubDate>Mon, 16 Nov 2026 04:58:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Identity &amp; Access</category><description>La Poste told AFP on November 14, 2026 that its subsidiary Maileva, a business mail-sending platform, lost the first names, last names and postal addresses of 22 million people in a mid-September attack. What is confirmed, what is not, and what teams that upload recipient lists to a mailing platform should check.</description><enclosure url="https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/cover_hu9769130884933775299.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/cover_hu9769130884933775299.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/cover_hu9769130884933775299.jpg" alt="A tall, untidy stack of opened envelopes and papers in white, pink, green, yellow and purple, shot close up with a shallow depth of field" width="1200" height="630"></p><p>La Poste has confirmed that Maileva, its group&rsquo;s online platform for sending business mail, lost the names and postal addresses of 22 million people in an attack in mid-September 2026. The company disclosed the figure to AFP on Saturday, November 14, almost two months after it took the whole platform offline. Bank details are not affected, according to La Poste. The affected people are mostly not Maileva&rsquo;s customers but the recipients of letters those customers sent, which makes this a supply-chain data breach for thousands of French organizations.</p>
<h2 id="what-happened">What happened</h2>
<p>Maileva is a subsidiary of Docaposte, itself part of the La Poste group. It describes itself as a &ldquo;Plateforme spécialisée dans l&rsquo;envoi de courriers pour les entreprises&rdquo; (a platform for sending business mail) and claims more than 70,000 users and 180 million documents sent in 2024, according to <a href="https://fr.news.yahoo.com/cyberattaque-maileva-filiale-poste-22-081810170.html">Euronews</a>.</p>
<p>On November 14, La Poste told AFP that Maileva &ldquo;a été victime à la mi-septembre d&rsquo;un vol des coordonnées de 22 millions de personnes&rdquo; (was the victim in mid-September of a theft of the contact details of 22 million people), as reported by Euronews. In a written response published by <a href="https://www.cyberattaque.org/maileva-docaposte-la-poste-cyberattaque/">Cyberattaque.org</a> on November 13, Maileva said: &ldquo;22 millions de personnes sont concernées par le vol de leurs données d&rsquo;identification : prénom, nom, adresse postale&rdquo; and &ldquo;Plusieurs milliers d&rsquo;entreprises clientes de Maileva sont concernées par cet incident&rdquo; (several thousand Maileva business customers are concerned).</p>
<h2 id="timeline">Timeline</h2>
<table>
  <thead>
      <tr>
          <th>Date (2026)</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Mid-September</td>
          <td>Data theft, per La Poste</td>
          <td>La Poste via AFP/Euronews</td>
      </tr>
      <tr>
          <td>September 23, 07:00</td>
          <td>Maileva suspends all services; tells clients of unauthorized access attempts by a cybercriminal seeking to send mail illegitimately</td>
          <td>Docaposte and Maileva client message, via <a href="https://www.solutions-numeriques.com/cyberattaque-maileva-six-jours-de-coupure-apres-une-tentative-de-detournement-de-la-plateforme/">Solutions Numériques</a></td>
      </tr>
      <tr>
          <td>September 24</td>
          <td>Incident first reported publicly by Cyberattaque.org and FrenchBreaches</td>
          <td>Solutions Numériques</td>
      </tr>
      <tr>
          <td>September 29</td>
          <td>Docaposte: services &ldquo;de nouveau pleinement opérationnels&rdquo; (fully operational again)</td>
          <td>Solutions Numériques</td>
      </tr>
      <tr>
          <td>November 13</td>
          <td>Maileva&rsquo;s written response puts the toll at 22 million people</td>
          <td>Cyberattaque.org</td>
      </tr>
      <tr>
          <td>November 14</td>
          <td>La Poste confirms the 22 million figure to AFP</td>
          <td>Euronews, <a href="https://www.moroccoworldnews.com/2026/11/346483/france-cyberattack-on-la-poste-subsidiary-exposes-data-of-22-million-people/">Morocco World News</a></td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Status</th>
          <th>Who says so</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Names and postal addresses of 22 million people stolen</td>
          <td>Confirmed by the company</td>
          <td>La Poste (AFP), Maileva (written response)</td>
      </tr>
      <tr>
          <td>Bank details and other personal information not affected</td>
          <td>Company statement</td>
          <td>La Poste (AFP)</td>
      </tr>
      <tr>
          <td>Several thousand business customers affected</td>
          <td>Company statement</td>
          <td>Maileva</td>
      </tr>
      <tr>
          <td>CNIL notified, complaint filed, judicial investigation open</td>
          <td>Company statement</td>
          <td>La Poste (AFP), Maileva</td>
      </tr>
      <tr>
          <td>Attacker tried to use client accounts to send mail</td>
          <td>Company statement (September)</td>
          <td>Maileva client message, Docaposte</td>
      </tr>
      <tr>
          <td>About 39 million references deduplicating to ~22 million people</td>
          <td><strong>Not confirmed publicly.</strong> Comes from internal documents attributed to Docaposte</td>
          <td>Cyberattaque.org</td>
      </tr>
      <tr>
          <td>Full contents of letters stolen</td>
          <td><strong>Not reported.</strong> Cyberattaque.org notes the 22 million figure covers identity and address, not that every letter was taken</td>
          <td>Cyberattaque.org (editorial analysis)</td>
      </tr>
      <tr>
          <td>How the attacker got in (stolen passwords, missing MFA, a platform flaw)</td>
          <td><strong>Not disclosed</strong></td>
          <td>Solutions Numériques reports no new findings from Docaposte</td>
      </tr>
      <tr>
          <td>Who did it</td>
          <td><strong>Not attributed</strong>; no public claim found</td>
          <td>None of the sources reviewed</td>
      </tr>
  </tbody>
</table>
<h2 id="how-the-attack-worked-as-far-as-sources-say">How the attack worked, as far as sources say</h2>
<p>Very little is public. In September, Maileva told customers it had detected &ldquo;des tentatives d&rsquo;accès non autorisé par un cyber criminel afin de procéder à l&rsquo;envoi illégitime de courriers&rdquo; (unauthorized access attempts by a cybercriminal in order to send mail illegitimately), according to Solutions Numériques. Docaposte described &ldquo;tentatives d&rsquo;accès non autorisées à la plateforme&rdquo;. The response reported at the time was to block the accounts concerned and stop the whole service as a precaution; Maileva also told individual customers that their own account had not been used and that no mail had been sent from their client space or API portal.</p>
<p>What is not public is the link between those access attempts and the data theft La Poste now dates to mid-September: whether the addresses were taken through compromised customer accounts, through the API, or from Maileva&rsquo;s back end. We are not going to guess.</p>
<h2 id="what-it-means-for-teams-that-use-a-mailing-platform">What it means for teams that use a mailing platform</h2>
<p>Maileva&rsquo;s model is common: a business uploads a document and a recipient list, and the provider prints, posts or sends it. The provider ends up holding a large, cross-customer store of names and addresses. Three things follow, whichever vendor you use.</p>
<p><strong>You may be the one who has to notify.</strong> Maileva said: &ldquo;L&rsquo;information des personnes concernées relève des organisations clientes de Maileva&rdquo; (informing the people concerned is up to Maileva&rsquo;s client organizations). Under <a href="https://gdpr-info.eu/art-33-gdpr/">GDPR Article 33</a>, &ldquo;the processor shall notify the controller without undue delay after becoming aware of a personal data breach&rdquo;, and the controller then has the 72-hour clock to the supervisory authority. If you use a mail or print-and-post service, check your contract&rsquo;s breach-notification clause and who on your side receives that notice.</p>
<p><strong>Lock down sending accounts like production credentials.</strong> The attacker&rsquo;s stated goal was to send mail from customer accounts. A sending account can mail anyone in your name, so it deserves the controls you would put on a payments or email-sending API:</p>
<ul>
<li>Turn on multi-factor authentication for every user of the portal, and remove shared logins.</li>
<li>Scope API keys to the minimum (send only, no address-book export if the vendor supports it), store them in a secrets manager, and rotate them after any vendor incident.</li>
<li>Restrict API access by source IP where the vendor offers it.</li>
<li>Ask for sending and login logs, and alert on sends outside your normal volume, hours or templates.</li>
</ul>
<p><strong>Minimise what sits at the vendor.</strong> Check how long the platform keeps uploaded recipient lists and sent documents, and delete or shorten retention where you can. A list that was purged after posting cannot be stolen months later. Our <a href="/posts/vetting-third-party-saas-tools-before-they-touch-your-data/">third-party SaaS vetting guide</a> has a checklist for these questions.</p>
<p><strong>Expect follow-on fraud.</strong> Names and postal addresses alone are useful for convincing phishing letters and calls that cite a real past letter from a known sender. If your organization sent mail through Maileva, tell customers how you will and will not contact them.</p>
<p>The pattern is the same one we saw when a single AI vendor breach exposed customer data at <a href="/posts/notion-ai-chats-exposed-fireworks-ai-breach-what-we-know/">Notion and others</a>: the incident is at the supplier, the obligations land on its customers.</p>
<h2 id="limits-of-this-article">Limits of this article</h2>
<p>Two French outlets that reported the 22 million figure, Franceinfo and Ouest-France, could not be retrieved for this article. We rely on Euronews&rsquo;s AFP-based report, Cyberattaque.org&rsquo;s published Maileva response and Solutions Numériques&rsquo;s September reporting. We did not retrieve a statement from Maileva&rsquo;s or La Poste&rsquo;s own websites. We will add a dated update if the company discloses the access method or the CNIL comments.</p>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>22 million people, mid-September theft, names and postal addresses, bank details not affected, CNIL and complaint</td>
          <td><a href="https://fr.news.yahoo.com/cyberattaque-maileva-filiale-poste-22-081810170.html">Euronews via Yahoo Actualités, Nov 15 2026 (AFP)</a></td>
          <td>Verified (company statement as reported)</td>
      </tr>
      <tr>
          <td>Maileva written response: 22 million, several thousand client companies, customers inform individuals</td>
          <td><a href="https://www.cyberattaque.org/maileva-docaposte-la-poste-cyberattaque/">Cyberattaque.org, Nov 13 2026</a></td>
          <td>Verified (company statement as published)</td>
      </tr>
      <tr>
          <td>39 million references from internal documents</td>
          <td>Cyberattaque.org</td>
          <td>Qualified (not confirmed by the company)</td>
      </tr>
      <tr>
          <td>Sept 23 suspension, Sept 29 restoration, access attempts to send mail, accounts blocked</td>
          <td><a href="https://www.solutions-numeriques.com/cyberattaque-maileva-six-jours-de-coupure-apres-une-tentative-de-detournement-de-la-plateforme/">Solutions Numériques, Sep 30 2026</a></td>
          <td>Verified (company statements as reported)</td>
      </tr>
      <tr>
          <td>La Poste confirmed to AFP on Nov 14</td>
          <td><a href="https://www.moroccoworldnews.com/2026/11/346483/france-cyberattack-on-la-poste-subsidiary-exposes-data-of-22-million-people/">Morocco World News, Nov 15 2026</a>, Euronews</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Processor-to-controller notification duty</td>
          <td><a href="https://gdpr-info.eu/art-33-gdpr/">GDPR Article 33</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Access method, attribution</td>
          <td>No source</td>
          <td>Not disclosed</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>