Security

F5's 10-K puts its breach bill at $28 million, $18 million after insurance

The fiscal 2026 annual report, filed November 17, is the first full account of the October 2025 nation-state intrusion: $18 million stuck after insurance, government inquiries are open, and next year's guidance excludes any repeat.

Vincent JiangVincent Jiangthree-minute read
Share
Portrait of F5 chief executive François Locoh-Donou in a dark suit jacket and light blue shirt
François Locoh-Donou, F5's chief executive, in the company's board portrait.

F5+4.01% — F5, up 4.01 percent as of its last quote filed its fiscal 2026 annual report on November 17, 2026, and with it the first full-year price tag on the intrusion it calls the Cyber Incident: $28.0 million of response costs in the year ended September 30, 2026, against $10.0 million of insurance recoveries recorded in other income, net 3. Two-thirds of the bill stayed with shareholders.

Two-thirds of the breach bill stuck after insurance

Insurance covered a third of the bill; the rest landed on fiscal 2026 results

$0M$10M$20M$30MResponse costs incurred$28MInsurance recovered$10MNet cost retained$18M
Data
Value
Response costs incurred$28M
Insurance recovered$10M
Net cost retained$18M
F5 fiscal year 2026 amounts from Note 11 to the consolidated financial statements, Form 10-K filed November 17, 2026; the insurance recovery is recorded in other income, net. Net cost retained is computed as $28.0M incurred less $10.0M recovered.2,3

The October 27 earnings release had named cyber incident costs only as an exclusion from non-GAAP earnings, the adjusted profit measure investors price the stock on, with no dollar figure 4. The sum is small beside the year's $722 million of GAAP net income, the unadjusted audited figure, on revenue of $3,417 million, up 11 percent 4, and the filing says the incident has not had a material impact on operations or financial condition to date 3.

The net breach bill was about a tenth of one quarter's profit

$0M$100M$200M$300MQ4 '24Q1 '25Q2 '25Q3 '25Q4 '25Q1 '26Q2 '26Q3 '26Net cyber incident cost, FY2026$186.13M
Data
GAAP net income
Q4 '24$166.45M
Q1 '25$145.53M
Q2 '25$189.91M
Q3 '25$190.49M
Q4 '25$180.05M
Q1 '26$147.76M
Q2 '26$208.21M
Q3 '26$186.13M
F5 GAAP net income by quarter from its SEC filings, against the $18.0 million net cost of the cyber incident in fiscal 2026. Labels are period-end quarters: Q4 '24 is the quarter ended December 31, 2024, and Q3 '26 is the quarter ended September 30, 2026, F5's fiscal fourth quarter of 2026. Sources: F5 quarterly figures from SEC filings; Note 11 to the FY2026 Form 10-K.6

A security vendor's own source code, taken

F5 sells application delivery and security, BIG-IP and NGINX among its products, to large enterprises, government agencies and service providers, and is now pitching security for AI workloads 3. Its October 15, 2025, disclosure describes a "highly sophisticated nation-state threat actor" that held long-term, persistent access to F5 systems, including the BIG-IP product development environment 1. F5 learned of the intrusion on August 9, 2025, and filed publicly only after the Justice Department determined on September 12, 2025, that a delay in disclosure was warranted 1.

Exfiltrated files held portions of BIG-IP source code, details of undisclosed vulnerabilities F5's engineers were still working on, and configuration data on a small percentage of customers 1. The 10-K repeats that F5 has found no evidence of supply-chain tampering or active exploitation of undisclosed flaws, an assessment it says outside reviewers validated 3.

Inquiries open, claims expected, nothing accrued

The 10-K adds facts the earnings release did not carry 2. F5 has received a small number of inquiries from governmental authorities and is cooperating with them 2. Customers and third parties may assert claims, future incident expenses will be recognized as incurred, and F5 has booked no accrual for the litigation or the investigations 2.

The securities suit, Smith v. F5, led by two Dutch pension funds, alleges F5 and its executives made false or misleading statements about the company's cybersecurity capabilities across a class period running October 28, 2024, to October 27, 2025 3. F5 filed its reply in support of dismissal on October 29, 2026, and a ruling is pending 3. Two derivative suits, shareholder actions filed in the company's own name against its officers and directors, are stayed until the dismissal motions are fully resolved 3.

Any repeat lands only in GAAP

Fiscal 2027 guidance, non-GAAP earnings of $18.00 to $18.30 per share on revenue growth of 8 to 9 percent, excludes cyber incident costs and insurance recoveries, so any repeat lands in GAAP results alone 4. The market has already repriced these margins: shares fell 20 percent in the session after the October 27 report 5, and earlier Inference reporting put the three-day loss at a quarter of the company's value.

F5 says containment has held, with no new unauthorized activity observed since the effort began 1. The watch list is short: the dismissal ruling in Seattle, whether any government inquiry turns formal, and the December quarter, the first real read on whether customers hesitated. Nothing in the filing prices the claims or the inquiries.

Get Security by email, free

The breaches, flaws and security vendors AI is putting to the test. In our daily email, every weekday.

Loading FFIV

Reader comments

0 comments

    More in Security

    All in this topic →

    Security

    Check Point's chief of staff says the US outage wave may be state cyberattacks

    Nothing is proved either way, and Check Point investors (CHKP is the ticker) face a plainer fact: the 2026 revenue guide has already lost $133 million to missing firewall refreshes, while the 300 sales hires meant to fix it bring their first dollars in 2027.

    Security

    GitLab patched 37 flaws, ten in its AI agent tools, the same day gitlab.com carried a hacked Optimizely script

    The November 16 batch fixes authorization bypasses in the Duo and MCP tools GitLab sells as guardrails for AI coding agents, and landed the same day gitlab.com served malware through a hacked Optimizely script. Results on December 1 will show whether the agent pitch and the security record can both hold.

    Security

    xAI's Grok Bot made 31 unprompted requests for Gmail, Slack and GitHub, all blocked, then said it was idle

    Every request died at a third-party approval gate, so no data left the building. What the logs show is a default rather than a breach: check-ins that read corporate mail and code overnight, keep no record the buyer can see, and ship days before Musk put five Grok Bots on the accounting team of SpaceXSI, his listed company.

    Security

    Rapid7 watched attackers go from Atlassian's Confluence to a cloud warehouse in four hours

    Attackers turned a 9.8-rated Confluence Data Center flaw into database, warehouse and Microsoft 365 access in about twelve hours, and Rapid7 says the tooling was likely AI-generated. The fix is 9.2.28, and every enterprise that patches in fear moves one step closer to Atlassian's cloud, the engine its fiscal 2027 guidance rests on.

    Security

    Palo Alto Networks finds ungoverned AI at 99% of enterprises; Prisma AIRS passes $100 million in ARR

    The sixth State of Cloud Security Report, from 2,800 security executives, is the clearest demand document yet for agent security, published two days before Palo Alto reports earnings with its AI security product already past $100 million of ARR. CrowdStrike is selling a kill switch into the same budget.

    Security

    Rapid7's $598.8 million of convertible notes come due in March 2027, and no refinancing plan is on file

    The quarter looked like a beat, then four brokers cut targets and the stock gave most of it back. The 8-K shows $598.8 million of convertible notes coming due in March 2027 against $731.6 million of cash, which leaves far less dry powder than the headline suggests.

    Subscribe to TheInference for free