Bullhorn says the staffing platform is back after an October 17 cyber incident. It also says a data-loss finding is not finished.
Bullhorn says the staffing platform is back after an October 17 cyber incident. Whether customer data left is still not determined. The status page is the company's clock.
The short version
Bullhorn says that on October 17 it detected a cyber incident and disabled access while working with CrowdStrike, and that on the morning of October 20 service had been restored and was being monitored. It warns customers that someone may pretend to be Bullhorn and ask for a password. Whether data was taken is, in the accounts of its FAQ, not yet determined.
Three days on the status page
Bullhorn's status page shows an October 17, 2026 sequence: a system-wide outage in the morning, then an update that a cyber incident had been detected and access disabled to contain it, with CrowdStrike named as the specialist on the investigation. Updates through October 19 say the investigation continued. On October 20 at 7:40 a.m. Eastern the page said a fix was in place, service had been restored, and monitoring continued. The Register's story that day is the account on the security wire.the advisory is the story.
The warning that rides with the restoration
The October 20 update asks customers to be wary of people posing as Bullhorn staff by email, text, or phone and using the incident as a reason to request credentials. It says Bullhorn will not ask for a password, a multi-factor code, or a verification token on those channels. That is a customer warning. It is not a description of how the incident started, and this page will not add one.the security desk.
Data loss is still an open sentence
BleepingComputer's October 19 article says Bullhorn's FAQ reported a forensic investigation underway and not yet a determination of whether customer data was taken. It says the company promised to notify affected people if a breach is confirmed. The Register's October 20 piece covers the outage. Neither article is a breach notice with a list of fields. Until that notice exists, restored logins and a completed data assessment are different facts. Asked directly, What does restored not mean? BleepingComputer's October 19 account, and Bullhorn's limitations note updated that day, describe features still offline or rebuilt, including job publishing and the legacy SOAP API. A status line that says service is restored can sit next to a list of features that are not.ETS and a different notice.
What came back, and what the limitations page still lists
BleepingComputer says Bullhorn described more than 10,000 customers and listed major products, including the talent platform, as disrupted on October 19, with some products still up. Bullhorn's own limitations note, updated October 19, says features were removed and had to be rebuilt: admin setup, several integrations, the legacy SOAP API, and job publishing among them. An October 20 restoration line does not erase that list. A reader checks the status page for which line is newer.Futureweb.
Passwords, as the company's instruction
BleepingComputer says the latest update it saw required non-SSO users to reset passwords at the next login, and that API passwords would be rotated. That is Bullhorn telling its customers what to do. This page does not repeat a procedure, a path, or a setting name beyond that instruction. CrowdStrike is the firm the status page says is helping. Naming the firm is not a finding about the intrusion. Asked directly, Who is in scope? Bullhorn's staffing and recruitment platform. BleepingComputer says the company describes itself as serving more than 10,000 customers. The Register's October 20 story is the security wire's account of the outage.
What this page will not speculate
It will not name a method, a family of intrusion, or a suspect. It will not treat more than 10,000 customers as a count of people affected. It will not read a restored platform as proof that nothing left. The FAQ's not yet determined is the careful sentence, and it is the one this page keeps. Asked directly, Has the company said customer data was taken? BleepingComputer, citing Bullhorn's FAQ on October 19, says a forensic investigation had started and had not yet determined whether customer data was exfiltrated, and that affected people would be notified if a breach is confirmed. Restored service is not that determination.
What would change the record
A breach notice that names categories of data and who was affected. A status correction that says access was not actually restored. A Bullhorn post that closes the forensic question. The Register and BleepingComputer are accounts. The status page is the company's clock. Asked directly, What did it say on October 20? At 7:40 a.m. Eastern, the status page said service had been restored and monitoring continued, and it warned that someone might pose as Bullhorn by email, text, or phone and ask for a password or a multi-factor code. It said Bullhorn will not ask for those.WhatsApp's help notes are a different incident.
Who the platform is for
Bullhorn sells software that staffing firms use to track candidates, onboarding, and related work. The outage is theirs and their customers'. A recruitment record is in scope only if a later notice says so. This page does not have that notice. Asked directly, What did Bullhorn say on October 17? That it had detected a cyber incident on the platform, temporarily disabled access to contain it, and was working with CrowdStrike. Earlier that day it had described a system-wide outage without yet using the words cyber incident.
What stays on the record
October 17 for the incident and the shutdown, CrowdStrike named by the company, October 20 for a restoration-and-monitor line plus an impersonation warning, and a data-loss question the FAQ had not answered as of the October 19 accounts. The short answer this page will stand on is this: Bullhorn says that on October 17 it detected a cyber incident and disabled access while working with CrowdStrike, and that on the morning of October 20 service had been restored and was being monitored. It warns customers that someone may pretend to be Bullhorn and ask for a password. Whether data was taken is, in the accounts of its FAQ, not yet determined.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
What did Bullhorn say on October 17?
That it had detected a cyber incident on the platform, temporarily disabled access to contain it, and was working with CrowdStrike. Earlier that day it had described a system-wide outage without yet using the words cyber incident.
What did it say on October 20?
At 7:40 a.m. Eastern, the status page said service had been restored and monitoring continued, and it warned that someone might pose as Bullhorn by email, text, or phone and ask for a password or a multi-factor code. It said Bullhorn will not ask for those.
Has the company said customer data was taken?
BleepingComputer, citing Bullhorn's FAQ on October 19, says a forensic investigation had started and had not yet determined whether customer data was exfiltrated, and that affected people would be notified if a breach is confirmed. Restored service is not that determination.
Who is in scope?
Bullhorn's staffing and recruitment platform. BleepingComputer says the company describes itself as serving more than 10,000 customers. The Register's October 20 story is the security wire's account of the outage.
What does restored not mean?
BleepingComputer's October 19 account, and Bullhorn's limitations note updated that day, describe features still offline or rebuilt, including job publishing and the legacy SOAP API. A status line that says service is restored can sit next to a list of features that are not.