Skip to content
cisonews.net

Incident · 8-K Item 8.01; Item 1.05

Boston Scientific reports a global disruption and a likely miss on 2026 guidance

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

Boston Scientific Corporation told the SEC on August 26, 2026 that it identified a cybersecurity incident on August 25, 2026 that disrupted its operations worldwide, and a follow-up filing on September 8, 2026 said the effects were likely material. The filings describe operational and financial effects and do not state that any personal information was involved or give a count of affected people.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at Boston Scientific, and when?

The first filing, made under Item 8.01, said the company activated its response protocols on detection and began an investigation with outside cybersecurity experts. It said access to some information systems and business applications was limited, including the handling of customer orders.

The September filing, made under Item 1.05, described unauthorized activity that led to a network outage. It added that the outage hindered manufacturing as well as order handling.

Has Boston Scientific recovered from the attack?

By the September filing, the company reported progress in its distribution network and at production sites. Sterilization facilities were running and most plants had restarted. The company did not give a date for full recovery.

What did Boston Scientific first say about the financial effect?

The company moved from undecided to a finding of likely material impact. In August it said it had not yet decided whether the incident was reasonably likely to be material. In September it said the third quarter and full year 2026 results would likely be affected. It expects to win back part of the lost revenue but called the full impact unknown. It does not expect a material effect on long-term financial condition.

What did Boston Scientific's third-quarter report show?

Boston Scientific's 10-Q for the quarter ended September 30, 2026, filed on November 2, 2026, puts the scale on record. It says the incident affected certain IT systems and caused a global disruption that hit its ability to manufacture and to process and ship customer orders. It also says the incident materially affected third-quarter results.

The gross margin bridge in the report gives the incident its own line, "abnormal production variances":

PeriodGross margin a year earlierEffect of the incidentGross margin, 2026
Third quarter69.9%(1.7)%66.7%
First nine months68.8%(0.5)%69.0%

The company says higher manufacturing and supply chain costs from idle production time were a main factor in the third-quarter margin. Disruptions to manufacturing and order fulfilment held back third-quarter net sales, and the report names the incident as a cause of sales declines in its Endoscopy and Urology businesses. It also lists incremental expenses from the incident among the drivers of selling, general and administrative costs, and higher incident costs as an offset to nine-month net income growth.

The report gives no single dollar figure for the incident.

What is still unknown?

The investigation was still running at the time of the September filing, and the company said it had found no sign of continuing access. The filings do not say how the intrusion began, whether any data was taken, or who may be affected. The company planned to give an outlook update on its third-quarter call on October 28, 2026.

How this disclosure's timing compares

Boston Scientific disclosed 1 day 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 life sciences & medical devices incidents on cisonews.net

  • Dexcom, Inc., Breach notice, first disclosed November 13, 2026
  • LeMaitre Vascular, Inc., Breach notice, first disclosed September 18, 2026
  • Amgen, 8-K Item 1.05, first disclosed July 31, 2026; 39,594 affected in total (Indiana Attorney General)
  • Fresenius Kabi USA, LLC, Breach notice, first disclosed June 17, 2026
  • iRhythm Holdings, 8-K Item 1.05, first disclosed June 15, 2026; 8,179,772 affected in total (HHS Office for Civil Rights)

All life sciences & medical devices incidents

Sources

  1. 2026-08-26 · ABoston Scientific Corporation, Form 8-K (SEC EDGAR), published August 26, 2026
  2. 2026-09-08 · ABoston Scientific Corporation, Form 8-K, Item 1.05 (SEC EDGAR), published September 8, 2026
  3. 2026-11-02 · ABoston Scientific Corporation, Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 2, 2026
  4. 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.