Skip to content
TOP NOW Did a Russian Lab Worker's Death Spark a New Plague Pandemic? / Instagram's New AI 'Muse': Creativity or Algorithmic Exploitation? / UK “rape capital” claim — what police data actually allows you to say
Rent Free News home rentfreenews. Claims vs data
Subscribe

The Biggest Data Leaks of 2026 and What They Exposed

From a decade-old PHP flaw to a live SMS database and a 2.8-million-patient genomics breach, here is what the 2026 data exposure wave actually revealed.

Y
By Yash • Contributing Writer
Published • Updated
Share

Primary source: PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet →

Viral claim - Global cybersecurity incident logs and threat advisories, 2026
"Unprecedented cyberattacks and foundational software bugs exposed the personal records of billions in 2026."
The Biggest Data Leaks of 2026 and What They Exposed
Illustration: Rent Free desk — By the Numbers
Why it matters

Foundational infrastructure flaws and stolen medical records cannot be reset like passwords, permanently shifting digital security risks.

Short answer: The 2026 data exposure wave was not defined by a single mega-breach. It combined a decade-old flaw in the PHP engine that put most of the web at risk, a live SMS database that leaked authentication codes in real time, a confirmed State Bank of India exposure, and a genomics breach affecting 2.8 million patients. Each incident exposed a different kind of permanent risk.

Correction (2026-11-15): An earlier revision removed unsupported claims about a 2026 Meta biometric exposure, a national telecom subscriber dump and a hospital genetic-data auction. This revision replaces the CSCTelecom section’s original Cybernews citation, which our source check could not retrieve, with BB.LV reporting. The October 27 closure date has been dropped as unverified, and the incident is now described only in the terms BB.LV published.

1. What the leak logs show

Over the past year, enterprise security defenses faced intense pressure. Corporate networks struggled as zero-day disclosures collided with automated scanning tools. Instead of targeting single corporate servers, attackers focused on shared software engines and third-party service providers.

When foundational open-source components break, thousands of independent organizations suffer at the same moment. At the same time, centralized registries and service providers accumulated massive volumes of citizen data. That centralization turned single configuration errors into national events. Stolen files quickly moved from private hacker chats onto public dark web forums and Telegram networks.

The four incidents below represent the largest exposures measured by records leaked, affected systems, and long-term risk. Two are confirmed breaches. One is a vulnerability that exposed the web’s shared infrastructure. One is a disputed scrape that Meta says is old data.

2. The global PHP2Shell web infrastructure emergency

A pair of critical memory safety flaws inside the core PHP engine triggered an internet-wide emergency. Tracked under CVE-2026-109618 and CVE-2026-109619, the bugs scored 9.2 out of 10 on the Common Vulnerability Scoring System (CVSS). The vulnerability had remained hidden within PHP request termination routines for more than a decade, going back to PHP 5.4.

Security researchers discovered the defect using frontier machine learning models. Wiz Research said the flaws could allow unauthenticated attackers to execute code on affected servers or read sensitive process memory, including passwords, tokens, and API keys. Because PHP powers roughly 70% of the internet, the disclosure on October 21, 2026, prompted coordinated patching across cloud providers, hosting companies, and content-delivery networks.

Wiz’s follow-up telemetry found no confirmed end-to-end exploitation in its own honeypots in the first week, but it did record automated attempts using public exploit kits. CISA added the two CVEs to its Known Exploited Vulnerabilities catalog on October 26, 2026. Within days, Wiz observed an approximate 67% decrease in internet-exposed vulnerable machines. For technical analysis of this engine bug, read our breakdown of the PHP2Shell vulnerability.

3. The CSCTelecom live SMS database exposure

In November 2026, BB.LV reported that the Latvian branch of CSCTelecom had left a database containing more than 125 million SMS messages publicly accessible. The messages ran from October 2022 to September 2026, and the database was updated in real time, which meant an attacker watching it could intercept identity verification codes, password reset links and confidential information before the intended recipients saw them.

The exposure was not a static archive. BB.LV, reporting the Cybernews research team that found it, said the unsecured database sat on the ClickHouse platform and was discovered on September 28, 2026, with more than three million messages sent through the service in September alone. The database held messages from major banks, medical institutions, popular online stores and government organisations, and from Latvia’s national emergency service at number 112.

The organisations named in the reporting included Swedbank, SEB bank and airBaltic, alongside dozens of other companies. Although CSCTelecom primarily operates in Latvia, the leak also affected companies and individuals in Lithuania and Estonia. Cybernews reached out to CSCTelecom for comment.

The number needs one qualification before it is used as a victim count. A message is not a person, and the 125 million figure is text records accumulated across nearly four years. The same customer can appear in thousands of them.

4. State Bank and South Asian banking breach

South Asian financial institutions faced sharp scrutiny after dark web sellers advertised customer databases originating from public banking infrastructure. The seller published sample files from a claimed 375,000-row repository. Initial reports warned that unpatched backend APIs had exposed account balances, ledgers, and national identity documents.

In regulatory disclosures submitted to the stock exchange, State Bank of India verified that 3,897 customer files containing personal information were part of the circulating cache. The confirmed data included names, mobile numbers, branch identifiers, and internal Customer Information File (CIF) numbers. Crucially, forensic teams confirmed that core account balances, transaction ledgers, passwords, and payment card numbers were not breached. Read our complete investigation into the State Bank data breach and filing numbers.

5. The Baylor Genetics patient record breach

Baylor Genetics, a clinical genomics company based at the Texas Medical Center in Houston, disclosed that an unauthorized third party accessed part of its network between June 11 and June 17, 2026. The company completed its review on July 30 and confirmed that patient and employee information had been involved.

The breach was later added to the HHS Office for Civil Rights website with a total of 2,810,878 individuals affected. The exposed data varied by person and could include names, dates of birth, medical testing information, lab test results, health insurance information, and, for a limited subset of patients, Social Security numbers. Employee data included Social Security numbers, government identification numbers, and financial account information.

Baylor Genetics said its laboratory operations continued without interruption and that it was unaware of any actual or attempted identity theft or fraud involving the data. The company offered credit monitoring and identity theft protection to at least some patients. The case matters because genetic and diagnostic records cannot be reissued the way a credit card can.

6. What’s missing / the permanence footnote

Raw headlines often treat all leaked records as identical, but evaluating real-world harm requires looking at data permanence. When an incident exposes account passwords or credit card numbers, banks issue replacements and consumers update their credentials. The immediate financial danger resolves once systems invalidate the old tokens.

The 2026 exposure wave highlights the growth of non-resettable identifiers. Medical test results, phone numbers, home addresses, and family records cannot be replaced with a single click. When attackers link basic phone numbers to leaked bank and airline records, the threat shifts from automated card theft to high-stakes social engineering.

Institutions also face complex audit trails. As seen during recent banking sector reviews, determining whether a leak occurred inside core servers or at third-party contractors can take weeks. To understand how statistical disclosures and corporate risk reports are calculated, explore our guide on how to read rankings.

Sources to check yourself

  • Wiz Research: the PHP2Shell technical disclosure, CVE numbers, CVSS score, and 70% exposure estimate.
  • Wiz Research exploitation update: real-world exploitation attempts and remediation trends.
  • Datadog Security Labs: independent detection and remediation analysis for CVE-2026-109618 and CVE-2026-109619.
  • NCSC-NL: operational guidance and vulnerability tracking from the Dutch national cyber security centre.
  • BB.LV: the 125-million-message CSCTelecom exposure, the ClickHouse discovery on September 28, and the banks, medical institutions and emergency services exposed.
  • The Economic Times: the SBI filing confirming 3,897 exposed customer records.
  • HIPAA Journal: the Baylor Genetics breach and the 2,810,878 affected individuals.

Frequently asked questions

Q: Which 2026 data leak affected the largest number of individual users? A: Among the confirmed incidents here, the Baylor Genetics breach affected 2,810,878 individuals, according to the HHS Office for Civil Rights tally reported by the HIPAA Journal. CSCTelecom exposed more than 125 million messages, but messages are not the same as unique users.

Q: Did the PHP2Shell vulnerability only affect personal computers? A: No. PHP2Shell targeted server-side PHP runtimes, exposing cloud servers, content management platforms, and web hosting infrastructure. Wiz estimates PHP powers roughly 70% of the internet.

Q: What is the main danger if financial balances were not leaked? A: Leaked contact details and internal customer numbers allow scammers to run convincing impersonation scams and SIM-swapping attacks against verified account holders. The SBI filing confirmed names, mobile numbers, branch identifiers, and CIF numbers, but not balances or card numbers.

How we checked: archived claim → primary dataset / VOD timestamp → quoted human with permission → verdict + corrections link. Report an error.

Reader discussion

Conversation for this story opens with memberships. Until then: found an error? Report it — we correct visibly.

The Sunday footnote — free

5 viral claims, what was missing.

Join the 2-minute Sunday read. One creator test inside. No spam.

AKM Loved by curious readers + quoted creators
Contextual Coverage

Related News — More in By the Numbers

All By the Numbers →

Keep reading

View all →