Cybersecurity

Frontline Education Data Breach Affects 3.09 Million School Staff and Students

Published By Shivam Sharma9 min read
Frontline Education data breach, 3.09 million school staff and students affected

Frontline Education has told the Indiana Attorney General’s Office that a data breach in August affected 3,085,266 people, SecurityWeek reported on 9 November. The K-12 software provider says attackers got in through a flaw in a third-party product on 14 August, stole personal data from school district staff and students, and were contained the next day. The stolen data includes Social Security numbers, passport numbers, Medicaid IDs and student IDs.

The number matters because it is far larger than the picture that existed a week earlier. On 3 November, SecurityWeek reported that filings with five states added up to 1,298,917 people affected. Six days later, the total Frontline gave Indiana was 3,085,266, more than twice as many. The first filings covered only 42.1 percent of the people now known to be affected.

The total sat in public filings for 14 days before the press found it

Frontline filed breach notices with 11 states between 26 and 28 October. The 3,085,266 total appeared in the Indiana filing of 26 October and the Texas filing of 28 October; the other nine filings in the 11-state set state no total. SecurityWeek’s 9 November report was the first press account of it, 14 days after the Indiana filing carried the total (12 days after the last filing, Texas, on 28 October). The number was derivable from public records from 26 October; it took nearly two weeks for anyone to report it.

The state-by-state picture, from the filings as tracked by AcidPeak, shows how unevenly the breach landed:

State Residents affected Share of the 3,085,266 total
Texas 778,372 25.2%
South Carolina 493,535 16.0%
Indiana 66,157 2.1%
Washington 40,494 1.3%
Massachusetts 16,550 0.5%
Montana 9,719 0.3%
New Hampshire 7,475 0.2%
Vermont 2,985 0.1%

Texas alone accounts for a quarter of the victims. Indiana, the state whose filing carried the headline total, accounts for just 2.1 percent of it. The remaining states in the 11-state filing set, California, Iowa and Rhode Island, published no resident count, so their share sits inside the total without a number attached. Eight of the eleven filings carry a resident count, and they add up to 1,415,287 people, 45.9 percent of the total. Do not add the state figures together to manufacture a second total: the 3,085,266 figure is the company’s own count, reported to Indiana and Texas, and the state resident counts are subsets of it.

Frontline has not said how many school districts were affected. The districts surfaced one by one instead. Killeen Independent School District in Texas reported about 45,000 current and former employees potentially affected. Greenwood School District 50 in South Carolina said almost 17,000 current and former students were impacted. Methuen Public Schools in Massachusetts reported more than 1,600 school employees affected. Jefferson County Public Schools in Louisville, Kentucky, said more than 37,000 current and former employees may have been compromised. Those are individual district disclosures, not pieces of a total, and they show how little the early district-level reporting captured: using the districts’ own approximate figures, the four named districts together account for about 100,600 potentially affected people, about 3 percent of the confirmed total.

A two-day break-in, a 73-day wait for letters

The breach itself was brief. The wait for answers was not. Frontline’s own notice, published 26 October, says its security team identified a vulnerability in a third-party software product on 14 August that allowed unauthorized access to part of its environment beginning that day, and that the last day of unauthorized activity was 15 August. The company says it investigated with an independent cybersecurity firm, fixed the flaw, contacted law enforcement and strengthened its monitoring.

Date What happened Days since 14 August
Fri 14 Aug 2026 Frontline identifies a vulnerability in a third-party product; unauthorized access began that day, per its notice Day 0
Sat 15 Aug 2026 Last day of unauthorized activity; attack contained Day 1
Wed 23 Sep 2026 Frontline determines an unauthorized actor acquired personal information Day 40
Thu 1 Oct 2026 At least one district had received a notification by this date Day 48
Fri 2 Oct 2026 BleepingComputer reports the breach, framed as school-district employee data Day 49
Tue 13 Oct 2026 Frontline notifies Jefferson County Public Schools, nearly two months after the intrusion Day 60
Mon 26 Oct 2026 Frontline publishes its public notice; individual notifications begin; first state filings Day 73
Tue 3 Nov 2026 SecurityWeek reports 1,298,917 people across five state filings Day 81
Mon 9 Nov 2026 SecurityWeek reports the 3,085,266 total from the Indiana filing Day 87

The scope of the story visibly widened as it went. On 2 October, BleepingComputer reported the breach as school-district employee data, quoting a district notice that listed Social Security numbers, email addresses and physical addresses. On 26 October, Frontline’s public notice confirmed that student-linked identifiers were in the exposed set too, including Student IDs and Medicaid IDs. The intrusion period did not grow in October; what grew was the confirmed scope of the data taken, with student-linked identifiers confirmed on 26 October.

What should I do if I got a Frontline letter?

If you got a letter or email from Frontline Education through Cyberscout, take it seriously: your Social Security number, passport number or a child’s student ID may have been taken. Enroll in the free monitoring offered, place a credit freeze, and check your statements. The steps below are general advice, not Frontline’s instructions.

  1. Enroll in the free TransUnion monitoring by 31 January 2027, using the code in your letter, or call 1-800-759-7279.
  2. Place a credit freeze at Equifax, Experian and TransUnion; it is free and blocks new accounts.
  3. Change any password you reused on school or district systems, then switch on two-step login.
  4. Check bank, card and health insurance statements monthly for charges or care you never received.
  5. Parents can request a free credit freeze for a child under 16, though bureaus may need a postal application.
  6. Report any misuse to the FTC at identitytheft.gov and to your local police, keeping copies of everything.

Frontline is offering adults in the United States two years of free credit monitoring, and cyber monitoring for minors, all through TransUnion. Its dedicated call center is 1-800-759-7279, 8 a.m. to 8 p.m. ET Monday through Friday, excluding major U.S. holidays. The letters come from Frontline Education through Cyberscout, and the company says individual notifications went by email or by letter sent through the U.S. Postal Service.

What was taken, and from which products

The data came from two Frontline products: Frontline Central, the employee management platform, and School Health Management, the student nursing documentation platform. What was taken varies by person, but Frontline’s notice lists Social Security number, date of birth, driver’s license number, passport number, other government ID, Medicaid ID and Student ID. Reporting adds names, addresses and email addresses to that list.

The mix is what makes this breach different from a typical consumer one. The highest-sensitivity exposure includes minors’ identifiers, Student IDs and Medicaid IDs, sitting alongside adults’ Social Security and passport numbers. That is why the remedy splits by age: credit monitoring for adults, cyber monitoring for minors. The split in the remedy is consistent with the student scope already confirmed in the notice, even though Frontline has published no count of how many of the 3,085,266 are students and how many are staff.

Frontline says it supports more than 10,000 K-12 organizations nationwide and is part of Roper Technologies. Its software runs human resources, student solutions (including School Health Management) and business operations for school districts, which is why one vendor’s breach reaches staff and students in districts across the country at once. Do not turn that footprint into a victim count: 10,000 organizations, 80,000 schools and 50 million students are figures for who Frontline serves, not who was affected. The affected number is 3,085,266.

What Frontline has not said

Three basic questions remain unanswered more than three months after the intrusion. Frontline has not named the third-party software product whose vulnerability was exploited. It has not named an attacker. And no known cybercrime group has claimed the attack, according to SecurityWeek.

Frontline says it is not aware of any examples of data misuse as a result of the incident, and that its experts have not seen any unauthorized activity since 15 August. That is the company’s own statement, not an independent finding.

The company also has not said how many districts were affected in total, or how the 3,085,266 splits between staff and students. Until it does, the state filings and the district disclosures are the only windows into the scale, and both understate it: the filings publish resident counts for only some states, and the districts that have spoken up so far account for about 3 percent of the total.

At least eleven class actions are already filed

Lawsuits followed quickly. At least eleven proposed class actions had been filed in federal court in Philadelphia by 6 November 2026, all in the U.S. District Court for the Eastern District of Pennsylvania. Marquitta Brooks, of West Memphis, Arkansas, filed the first on 5 October 2026 (No. 2:26-cv-07630), alleging negligence, negligence per se, unjust enrichment, breach of implied contract and breach of confidence. Shaw and Steinman followed on 6 October, Grant on 7 October, Denuto on 12 October, Rezayat on 13 October, Scarth on 19 October and Smith on 29 October. Bonnie Anderson, a Texas schoolteacher, filed on 2 November (No. 2:26-cv-08348). Her complaint says she received her notice, dated 28 October, about 75 days after Frontline identified the unauthorized access, while Frontline’s general individual notifications began on 26 October, 73 days after 14 August. She proposes a nationwide class and, in the alternative, a Texas-residents class, and points to a Texas law requiring notice within 60 days of determining a breach occurred. Jones filed on 3 November and Shawn on 6 November. The complaints allege Frontline failed to encrypt the data, patch the exploited vulnerability or give timely notice. The majority plaintiffs have already moved to consolidate the cases in the Brooks case, filing papers on 14 and 15 October and again on 2 November; no ruling had been reported.

These are allegations, not findings, and no settlement has been announced. The 73-day gap is central to Anderson’s complaint, which alleges untimely notice.

What to watch next

The first thing to watch is whether Frontline ever names the third-party product. That name matters because other school districts may use the same software, and a named flaw lets them check whether they are exposed through a different vendor. The second is any confirmed misuse report, which would contradict Frontline’s statement that it knows of none. The third is whether the court grants the consolidation already sought in the Brooks case (papers filed 14 and 15 October and 2 November), and which case leads the consolidated action. The fourth is whether a settlement opens a claims process for class members. The fifth is the district count: if Frontline discloses how many districts were hit, a district count would show what share of affected districts have spoken up.

This is a different kind of school breach from the district attacks reported in the same weeks. Those were attacks on individual districts. This was an attack on the vendor that sits behind thousands of districts, and the 3,085,266 total is the measure of what that position costs when it fails.