Skip to content
cisonews.net

Incident · 8-K Item 1.05

CareCloud data breach: a March 2026 disruption to one health record environment, 3,756,469 people

Compiled from public records. Updated 2026-11-13. By the cisonews.net Desk.

The CareCloud data breach affected 3,756,469 people, according to the federal health breach portal, where CareCloud, Inc. reported a hacking or IT incident as a business associate on July 24, 2026. CareCloud, Inc. told the SEC in an Item 1.05 Form 8-K dated March 27, 2026 that a temporary network disruption on March 16, 2026 partly affected one of its six electronic health record environments. The environment stores patient information, and the filing does not say whether any of it was accessed or taken, or how many people are affected. On July 24, 2026, CareCloud submitted a breach report to the Department of Health and Human Services counting 3,756,469 individuals affected (details below).

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at CareCloud, and when?

The disruption hit the company's CareCloud Health division and reduced functionality and data access in 1 of its 6 electronic health record environments. The company says it fully restored functionality and data access that evening.

CareCloud says it contained the incident on the day it was discovered. It also says the incident stayed within the CareCloud Health environment and did not touch its other platforms, divisions, systems, data or environments.

How did CareCloud respond, and what caused it?

The company reported the matter to its cybersecurity carrier and engaged an external advisory team to help secure the environment and run a forensic investigation. It says it believes an unauthorized third party temporarily had access to the system. It has also reported the matter to law enforcement authorities.

CareCloud says all affected systems are restored and that it believes the threat actor no longer has access to them.

What patient information was involved?

The filing names no data categories and gives no count of people. The company says it is still assessing whether and to what extent patient information or other data was accessed or exfiltrated, and the categories and volume of any such data. The filing does not mention a notification letter to patients.

Was the CareCloud incident material?

CareCloud says the incident had not had a material impact on its operations as of the filing date. On March 24, 2026 it nonetheless judged the incident material because of the sensitivity of the potentially affected information and the potential consequences, including remediation costs and legal, regulatory and notification-related matters.

The company does not expect a material effect on its financial condition or results of operations, though it has not yet determined the full impact. It believes its cybersecurity insurance coverage is sufficient for any potential losses.

What does CareCloud's November 2026 10-Q add?

CareCloud's 10-Q for the third quarter of 2026, filed on November 5, 2026, answers the question the 8-K left open. The forensic investigation found that an unauthorized third party got into one cloud account supporting one of the division's six electronic health record environments and took patient-related information, including personally identifiable information and protected health information, for a substantial number of individuals.

The environment lost functionality and data access for about eight hours on March 16, 2026. The investigation found no unauthorized activity after that day and no sign that any other platform, division, system or environment was affected. The company brought in a cyber response advisory team within a Big Four accounting firm. It says it has told its healthcare-provider customers and is sending the required notices to individuals and regulators under its agreements with those customers. It believes its cybersecurity insurance is likely to be sufficient for the losses it currently expects.

How many Washington residents were affected?

Washington's attorney general lists a report from CareCloud, Inc. on July 24, 2026, for a breach dated March 10, 2026, with 20,706 Washingtonians affected. The information it records as compromised is: name, Social Security number, driver's license or Washington ID card number, financial and banking information, full date of birth, health insurance policy or ID number and medical information. That count covers Washington residents only. CareCloud's report is one of the 20 largest in our ranking of Washington's 2026 notices.

How many Massachusetts residents were affected?

Massachusetts' Office of Consumer Affairs and Business Regulation lists a report from CareCloud, Inc. dated July 25, 2026 (breach 2026-1225): 72,102 Massachusetts residents affected. The categories it marks as breached are Social Security numbers, medical records, financial account numbers, driver's license numbers and credit or debit card numbers. That count covers Massachusetts residents only.

How many people were affected by the CareCloud breach?

The Department of Health and Human Services' Office for Civil Rights lists a breach report from CareCloud, Inc., filed as a business associate, submitted on July 24, 2026: 3,756,469 individuals affected, classed as a hacking or IT incident with the information on a network server. HHS posts breaches of protected health information that affect 500 or more people, and the figure is the count the organization reported to it. It was submitted on the same day CareCloud reported to Washington's attorney general.

What is still unknown?

The company commits to amend the report as missing Item 1.05 information is determined or becomes available. No 8-K amendment is on record. The November 10-Q describes the data taken but gives no count of people; the count comes only from the federal health breach list above.

How this disclosure's timing compares

CareCloud disclosed 11 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other health care incidents on cisonews.net

All health care incidents

Sources

  1. 2026-11-05 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2026 Data Breach Notification Report, published November 5, 2026
  2. 2026-11-05 · AU.S. Department of Health and Human Services, Office for Civil Rights, breach portal (breaches affecting 500 or more individuals), published November 5, 2026
  3. 2026-11-05 · AWashington State Office of the Attorney General, data breach notifications list, published November 5, 2026
  4. 2026-03-27 · ACareCloud, Inc., Form 8-K (SEC EDGAR), published March 27, 2026
  5. 2026-11-05 · ACareCloud, Inc., Form 10-Q for the quarter ended September 30, 2026, published November 5, 2026
  6. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.