Topic starter
06/06/2026 1:57 am
TL;DR: McDonald’s AI hiring platform exposed data from an estimated 64 million applicants after a default admin credential of 123456 and an IDOR flaw let researchers reach live records, according to Oasis Security. The case shows how weak NHI governance, not just application logic, can turn an AI workflow into a broad exposure event.
Editorial analysis by NHI Mgmt Group, based on content published by Oasis Security: “McDonald’s AI Hiring Tool Breach A Wake-Up Call for Non‑Human Identity Security”.
By the numbers:
- Enterprise AI adoption grew by 187% between 2023 and 2025, while security spending increased by only 43% during the same period.
Key questions
Q: What breaks when default credentials exist on an AI workflow account?
A: A default credential turns a non-human identity into a ready-made entry point, especially when the account sits behind a chatbot, hiring portal, or API gateway.
Q: Why do AI hiring platforms create higher exposure when object-level access is weak?
A: Because applicant records are often accessed through APIs that expose internal object identifiers, so one authorization flaw can turn into bulk record retrieval.
Q: How do teams know whether non-human identity controls are actually working?
A: Look for reduced use of shared credentials, fewer manually rotated secrets, shorter credential lifetimes, and clear ownership for each workload identity.
Practitioner guidance
- Eliminate default admin credentials Remove factory or test credentials from every AI workflow account before production and verify that no privileged bot login can be reused across environments.
- Inventory every non-human identity in hiring flows Build a complete register of bots, service accounts, API keys, and test admins that can touch applicant data, and assign explicit owners for each one.
- Enforce object-level authorization on applicant records Test every hiring API and admin workflow for sequential object access, and require server-side checks on each record before data is returned.
Bottom line: The breach shows that weak governance of non-human identities can turn an AI hiring workflow into a mass exposure event.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 5 days ago by NHI Mgmt Group
06/06/2026 3:20 am
Default credentials on non-human admin accounts are a governance failure, not a narrow configuration mistake. The McHire case shows that a single weak bot credential can expose production data if the organisation has not made non-human identity ownership, onboarding, and credential hygiene mandatory. In NHI terms, this is not just poor password discipline. It is evidence that the access model for automated workflows was never brought under the same control expectations as human admin access. Practitioners should treat every default credential on an AI workflow as a governance defect, not a local bug.
A question worth separating out:
Q: Who is accountable for AI workflow access when a hiring vendor and employer both touch the system?
A: Accountability should sit with the organisation that permits production access and owns the data, even when a vendor operates part of the workflow. Shared responsibility does not remove the need for explicit ownership of bot accounts, API privileges, and offboarding decisions.
👉 Read our full editorial: McDonald’s AI hiring tool breach exposes NHI governance gaps
This post was modified 5 days ago by NHI Mgmt Group