Bullhorn ATS/CRM cyber incident

A cyber incident interrupted Bullhorn ATS/CRM, with feature limitations continuing after access returned.

Last modified

Summary

  • Environment: Bullhorn ATS/CRM and connected service workflows
  • Operational impact: Platform access interrupted; regional access restored with limitations
  • Financial impact: No incident cost established in the reviewed evidence
  • Record status: Developing record. Reviewed November 2, 2026; updated as evidence emerges.

What happened

Bullhorn reported a widespread outage on October 17, 2026, then confirmed a cyber incident and disabled access for containment. CrowdStrike specialists assisted the response. [5]

Impact

Talent Platform was also disabled as a precaution and later restored. That interruption does not establish it was compromised. [4]

By October 20, all ATS/CRM regions were online, with customizations and password-reset issues still being addressed. Its October 20 FAQ had not determined whether customer data was stolen. [3][5]

On October 21, Bullhorn said separate PHP-related precautions and database-replication problems caused additional disruption. It described both as unrelated to the October 17 cyber incident. [2]

On October 24, Bullhorn reported all products available, with ATS Canvas still unavailable and some users experiencing login problems. This operational update did not resolve the earlier question of data theft. [2]

The October 27 update also listed the QuickBooks Desktop connector offline for Bullhorn Back Office customers, alongside continuing Canvas and login limitations. The status entry does not establish that the connector outage was caused by the cyber incident. [2]

By October 30 at 20:01 EDT, Canvas limitations had narrowed: adding and editing reports remained unavailable, while running, copying and deleting reports were unaffected. The QuickBooks Desktop connector remained offline, and Back Office login issues still required support. [2]

On November 2, Bullhorn said Back Office time entry worked with existing credentials and required no password changes. The QuickBooks Desktop connector remained offline; payroll or E-Verify integration problems required support. This guidance is specific to Back Office and does not replace the earlier ATS/CRM password-reset instructions. [1]

Timeline

  1. Outage and cyber incident confirmed

    The status notice recorded the outage at 08:04 EDT and confirmed the cyber incident at 15:28 EDT.

    [5]
  2. Regional access restored

    At 09:30 EDT, Bullhorn reported all regions online with monitoring and some limitations continuing.

    [5]
  3. Containment reaffirmed

    The master status update distinguished the cyber incident from other outages.

    [2]
  4. Availability and remaining limitations updated

    The all-products update reported availability with Canvas and login limitations.

    [2]
  5. Connector limitation added to status

    The all-products status update listed the QuickBooks Desktop connector offline for Back Office customers.

    [2]
  6. Canvas limitations narrowed

    The all-products status reports general availability with specific features still limited.

    [2]
  7. Back Office guidance clarified

    The BBO status update clarifies time-entry access and remaining connector limitations.

    [1]
  8. Briefing updated

    This briefing was last reviewed and updated on November 2, 2026.

Threat Group & Attack Vector

The initial access path and attacker identity remain unresolved.

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

Bullhorn required password resets for users without single sign-on and rotation of API passwords. Its FAQ said client-secret rotation was not yet required. Removing technology for security reasons also required rebuilding features. The investigation remained open. [3]

At 09:00 EDT on October 21, Bullhorn said the cyber incident remained contained, with no additional activity detected since October 17. CrowdStrike and Kroll were assisting monitoring. [2]

Bullhorn also identified an ATS single-sign-on issue affecting access to Bullhorn Back Office and directed affected users to support for a fix. [2]