Risks Shadow AI & credential theft

Elevated

Elevated: a bank reported a real incident after customer data went into an unapproved AI app, and it applies to organizations whose staff can reach such apps, but the harm is exposure of customer data, and the filing gives no count of affected customers. How we rate severity

Shadow AI risk: a bank disclosed a material incident involving an unauthorized AI app

A US bank holding company filed an 8-K on an incident involving customer data and an unauthorized AI app. It deemed the event material.

What happened

A Form 8-K filed with the SEC on May 11, 2026 shows shadow AI risk reaching a public company’s disclosure obligations.

In the filing, under Item 1.05 (Material Cybersecurity Incidents), CB Financial Services, Inc. says that on May 5, 2026, its wholly owned subsidiary Community Bank “became aware of an internal incident involving the handling of certain non‑public customer information using an unauthorized artificial intelligence-based software application.” The company says the bank “promptly took steps to secure the information at issue” and began an internal investigation with external cybersecurity advisors. It says that, as of the filing, the investigation, “including the scope and root cause, remains ongoing.”

The filing says the incident did not disrupt the bank’s operations, customer access to accounts or services, payment systems, or core IT infrastructure. However, “due to the volume and sensitive nature of the non-public information at issue,” the company determined on May 7, 2026 that the event was material. It says the customer information the bank has determined was disclosed includes “customer names, social security numbers and dates of birth.” The company says it is notifying customers as required, has been in contact with banking and financial regulators, and is taking steps to prevent similar incidents, including strengthening existing controls, adding controls, and enhancing monitoring. It says the incident has not had, and is not expected to have, a material impact on its financial condition or results of operations.

The filing does not name the AI application or describe how the information was handled.

Why it matters to leaders (our analysis)

This filing shows that the use of an unapproved AI tool can become a disclosable cybersecurity incident, with customer notification and regulator contact, even without any disruption to systems. The company’s own description is brief, and the filing said the scope and root cause were still under investigation, so it doesn’t support conclusions about what happened or why.

What it does show is where the question now sits. Which AI tools may touch regulated data, how use of other tools would be detected, and how such an event would be assessed for materiality are governance questions for leadership, not only IT.

What to tell your board

Staff putting customer data into unapproved AI apps can cause a reportable incident, so we publish approved tools, watch data going to AI services, and train staff on what's allowed.

What your board will ask

  1. Which AI tools are approved for work with customer or regulated data, and do staff know the answer?
  2. Could we detect sensitive customer data being sent to an AI service we haven't approved?
  3. Does our incident-response and disclosure process cover incidents caused by unapproved AI tools?
  4. Have we given staff an approved AI option for the tasks they're likely to try with unapproved ones?

Controls that help

  • Publish a short list of approved AI tools and the data each may handle, and make the approved option easy to use. NIST AI RMF — GOVERN
  • Apply data-loss prevention to AI destinations, including web chat, file upload, and browser extensions, with rules for identifiers such as Social Security numbers. ISO/IEC 27001:2022 A.8.12 Data leakage prevention
  • Include unapproved AI use in incident-response playbooks and materiality assessments. ISO/IEC 27001:2022 A.5.24 Incident management planning
  • Train staff on which AI tools may receive customer data, with examples from their own work. ISO/IEC 27001:2022 A.6.3 Information security awareness, education and training

Sources

  1. CB Financial Services, Inc. Form 8-K (Item 1.05, Material Cybersecurity Incidents) — U.S. Securities and Exchange Commission (EDGAR) · May 11, 2026

Published Oct 17, 2026 · Last updated Oct 17, 2026

Change log

  • Oct 17, 2026. First published.

All Shadow AI & credential theft risks

Other systems

Coming soon

The weekly AI security briefing

The five AI risks security leaders should know, with the questions your board will ask. Signups open soon.

Signups open soon. We'll never share your email. See our Privacy Policy. Privacy Policy

Sponsored

Your logo here: sponsor us →