Incident · 8-K Item 1.05
F5 discloses nation-state access to BIG-IP source code and vulnerability data
Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.
F5, Inc. told the SEC in an Item 1.05 Form 8-K dated October 15, 2025 that a highly sophisticated nation-state threat actor had gained unauthorized access to certain company systems, which it learned of on August 9, 2025. Files taken included portions of BIG-IP source code, information about undisclosed BIG-IP vulnerabilities, and configuration or implementation details for a small percentage of customers. The filing gives no count of affected people.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
Three later sources fill in what the 8-K left open. The same day F5 filed, CISA issued Emergency Directive 26-01, which ordered federal civilian agencies to inventory their F5 devices and install F5's updates. F5's annual report, filed on November 25, 2025, says outside research firms reviewed its finding that the software supply chain was not modified. Its quarterly reports put the cost of the response at $26.5 million for the nine months to June 30, 2026.
What did the F5 breach expose?
Some exfiltrated files held BIG-IP source code and details of vulnerabilities F5 was still working on. F5 says it knows of no undisclosed critical or remote code vulnerabilities and no active exploitation. It reports no evidence of changes to its source code or build and release pipelines.
Files from the knowledge management platform also touched customers. F5 says it is reviewing them and will contact affected customers directly as appropriate.
When did F5 find the attacker, and how long were they inside?
F5 says its investigation found long-term access to the BIG-IP product development environment and the engineering knowledge management platform. The company says it activated incident response and brought in outside cybersecurity experts. It reports no new unauthorized activity since containment began.
| Date | What happened | Source |
|---|---|---|
| August 9, 2025 | F5 learns a nation-state actor has access to some of its systems | 8-K |
| September 12, 2025 | The Justice Department finds a delay in public disclosure warranted | 8-K |
| October 15, 2025 | F5 files its Item 1.05 8-K; CISA issues Emergency Directive 26-01 | 8-K, CISA |
| October 22, 2025 | CISA's deadline for agencies to update BIG-IP F5OS, TMOS, BIG-IQ and BNK/CNF | CISA |
| October 31, 2025 | CISA's deadline to patch all other F5 devices | CISA |
| November 25, 2025 | F5's 10-K says containment is holding and its review was checked by outside firms | 10-K |
| February 5, 2026 | 10-Q reports $17.5 million of response costs in the December quarter | 10-Q |
| August 6, 2026 | 10-Q reports $26.5 million over nine months and $5.3 million of insurance recoveries | 10-Q |
The 8-K does not say when the access began, only that it was long-term.
What did CISA order agencies to do about F5 devices?
CISA's directive treats the stolen code as a risk to every agency running F5 equipment. It says the actor's access to F5's source code could give it a technical advantage in exploiting F5 devices and software. It also calls the actor an imminent threat to federal networks that use F5 devices and software.
The directive sets three deadlines. Agencies had to apply F5's latest update to BIG-IP F5OS, BIG-IP TMOS, BIG-IQ and BNK/CNF by October 22, 2025. Every other F5 device had to carry the latest patch by October 31, 2025. Agencies also had to disconnect and decommission public-facing F5 devices that had reached end of support. A full inventory was due to CISA by 11:59 PM ET on December 3, 2025.
The directive binds federal civilian agencies only. For a company that runs BIG-IP, the same list of products and the same two dates are the plainest public yardstick for how fast to patch.
Which F5 systems were not reached?
F5 reports no evidence of access to data from its CRM, financial, support case management, or iHealth systems. It also reports no evidence of access to NGINX source code or its development environment.
The 10-K adds two more product lines. F5 says it has no evidence that the actor reached or changed F5 Distributed Cloud Services or Silverline systems.
Why did F5 wait until October 15 to disclose?
The filing says the Department of Justice found a delay in public disclosure warranted on September 12, 2025. F5 says the incident has not had a material impact on operations and that it is still assessing financial effects.
The Item 1.05 guide explains how a Justice Department finding can hold back an 8-K, and sets F5's single determination beside AT&T's two.
What has the F5 breach cost so far?
F5's fiscal year starts in October, so the whole response falls in fiscal 2026. The first quarterly report, filed on February 5, 2026, puts the cost at $17.5 million for the three months to December 31, 2025. That quarter's general and administrative expenses rose by $9.3 million from incident costs, compared with a year earlier.
The 10-Q for the quarter ended March 31, 2026, filed on May 5, 2026, reports $6.0 million in that quarter and $23.5 million over the first six months. The next 10-Q, filed on August 6, 2026, adds $3.0 million, bringing the nine-month total to $26.5 million, and records $5.3 million of insurance recoveries.
| Report | Period | Response costs |
|---|---|---|
| 10-Q, filed May 5, 2026 | Three months to March 31, 2026 | $6.0 million |
| 10-Q, filed May 5, 2026 | Six months to March 31, 2026 | $23.5 million |
| 10-Q, filed August 6, 2026 | Three months to June 30, 2026 | $3.0 million |
| 10-Q, filed August 6, 2026 | Nine months to June 30, 2026 | $26.5 million |
| Report | Period | Response costs |
|---|---|---|
| 10-Q, filed February 5, 2026 | Three months to December 31, 2025 | $17.5 million |
| 10-Q, filed May 5, 2026 | Three months to March 31, 2026 | $6.0 million |
| 10-Q, filed May 5, 2026 | Six months to March 31, 2026 | $23.5 million |
| 10-Q, filed August 6, 2026 | Three months to June 30, 2026 | $3.0 million |
| 10-Q, filed August 6, 2026 | Nine months to June 30, 2026 | $26.5 million |
The quarterly figures fall from $17.5 million to $3.0 million, so most of the cost came in the first three months. The quarter to September 30, 2026, the last of F5's fiscal year, is not yet in the record. The guide to later 10-Q and 10-K filings shows how other companies in this log close out an incident in the same reports.
What did F5 tell investors to expect?
The annual report warned of a hit to sales. F5 said it expected near-term disruption to its sales cycles, with the effect on demand strongest early in fiscal 2026 and normalizing in the second half. It also said it had put software updates for every undisclosed high vulnerability in BIG-IP first. F5 reports that its investigation and monitoring were still going on.
What is still unknown?
F5 has not named the actor or said when the access began. It has not said how many customers' configuration files were taken, beyond "a small percentage". The filings give no count of affected people, because the stolen files were engineering material and customer configurations, not personal records.
How this disclosure's timing compares
F5 disclosed 67 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 technology incidents on cisonews.net
- DreamHost, Breach notice, first disclosed November 2, 2026
- Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
- Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
- Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
- IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)
Sources
- 2025-10-15 · AF5, Inc., Form 8-K (SEC EDGAR), published October 15, 2025
- 2026-05-05 · AF5, Form 10-Q for the period ended 2026-03-31 (SEC EDGAR), published May 5, 2026
- 2026-08-06 · AF5, Form 10-Q for the period ended 2026-06-30 (SEC EDGAR), published August 6, 2026
- 2025-11-25 · AF5, Form 10-K for the fiscal year ended 2025-09-30 (SEC EDGAR), published November 25, 2025
- 2026-02-05 · AF5, Form 10-Q for the period ended 2025-12-31 (SEC EDGAR), published February 5, 2026
- 2025-10-15 · ACISA, Emergency Directive 26-01: Mitigate Vulnerabilities in F5 Devices, published October 15, 2025
- 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.