Incident · 8-K Item 1.05
Navient reports borrower data exposed in a ransomware attack on an outside law firm
Compiled from public records. Updated 2026-11-08. By the cisonews.net Desk.
Navient Corporation told the SEC in an Item 1.05 Form 8-K dated July 2, 2026 that a ransomware attack on a third-party law firm gave an unauthorized actor access to Navient-related borrower data. The data includes customer names, dates of birth, addresses and Social Security numbers, and the filing does not state how many people are affected.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
Navient says it became aware of the incident on June 8, 2026. The filing describes a ransomware attack on certain of the law firm's information systems. Navient learned of the data access from the firm itself.
The data was held because the firm provided legal services to Navient. The filing does not name the firm.
What information was involved
The filing describes the data as borrower information. The word such in the filing signals examples, so the filing does not say whether other fields were included. It does not say which borrowers, loan types or states are affected.
Response and materiality
Navient says it opened an investigation with outside cybersecurity experts and is notifying people and regulators. Law enforcement has been notified.
Navient determined the incident was material on June 29, 2026, and tied that decision to the data rather than to any business disruption.
Effect on operations and finances
Navient says the incident stayed within the law firm's environment. It also reports no disruption to operations or customer services. On finances, the company does not expect a material impact.
What Navient's August 10-Q adds
Navient's 10-Q for the second quarter, filed on August 7, 2026, says Navient began working with the law firm on notices to affected people and to regulators as soon as it learned of the incident. It adds that Navient knows of no further disclosure or misuse of the personal information.
On money, the 10-Q says the incident had no material effect on Navient's results for the quarter, while repeating that the June 29 materiality call rested on the volume and sensitivity of the data. So the incident is material because of the data involved, not because of what it cost.
Where Navient's later filings come from now
Navient Corporation no longer files its own reports. On October 28, 2026 it completed a reorganization under which it merged into Navient LLC, now a wholly owned subsidiary of a new parent, Navient Holdings, Inc., and each Navient share became one Navient Holdings share. The old Navient stock stopped trading on Nasdaq before the open on October 29, 2026, and Navient filed a Form 15 to end the registration of that stock.
Any later word on the law-firm incident will therefore come from Navient Holdings. Its first quarterly report, for the period ended September 30, 2026 and filed on November 4, 2026, does not mention the incident. The August 10-Q, above, is still the latest filing that discusses it.
| Filed | Filer | What it says about the incident |
|---|---|---|
| July 2, 2026 | Navient Corporation, Form 8-K, Item 1.05 | The original disclosure |
| August 7, 2026 | Navient Corporation, Form 10-Q | Notices under way; no material effect on the quarter |
| November 2, 2026 | Navient Corporation, Form 8-K | Reorganization under Navient Holdings completed October 28 |
| November 4, 2026 | Navient Holdings, Form 10-Q | Nothing |
How other filers closed out an incident in later reports is in After the 8-K.
What data was exposed in the Navient law firm breach?
Borrower information held by an outside law firm, including customer names, dates of birth, addresses and Social Security numbers, per both the 8-K and the 10-Q.
Were Navient's own systems hacked?
No. Both filings say the incident was limited to the law firm's environment and Navient found no access to its own systems.
Why did Navient call it material if it cost little?
The company tied materiality to the volume and sensitivity of the data. Its 10-Q says the incident had no material effect on results for the quarter.
What the filing leaves open
Neither the 8-K nor the 10-Q gives a count of affected people, no date for the unauthorized access, and no information about what the attacker demanded or did with the data. They also give no notification timeline, no call-center details and no credit monitoring offer.
How this disclosure's timing compares
Navient disclosed 24 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 financial services incidents on cisonews.net
- ICW Group Holdings, Inc., Breach notice, first disclosed November 13, 2026
- Point72 Asset Management, L.P., Breach notice, first disclosed November 5, 2026
- The Vanguard Group, Inc., Breach notice, first disclosed November 4, 2026
- Hippo Analytics, Breach notice, first disclosed November 3, 2026; 176,128 affected in total (Indiana Attorney General)
- Baanx US Corp, Breach notice, first disclosed October 30, 2026; 6,594 affected in total (Indiana Attorney General)
Sources
- 2026-07-02 · ANavient Corporation, Form 8-K (SEC EDGAR), published July 2, 2026
- 2026-08-07 · ANavient Corporation, Form 10-Q for the quarter ended June 30, 2026 (SEC EDGAR), published August 7, 2026
- 2026-11-02 · ANavient Corporation, Form 8-K on the reorganization (SEC EDGAR), published November 2, 2026
- 2026-11-04 · ANavient Holdings, Inc., Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 4, 2026
- 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.