Incident disclosureDisclosed 2026-05-11CB Financial Services, Inc.SEC filing

CB Financial Services, Inc. discloses a cybersecurity incident (SEC 8-K, May 2026)

On May 5, 2026, Community Bank (the “Bank”), the wholly-owned subsidiary of CB Financial Services, Inc. (the “Company”), became aware of an internal incident involving the handling of certain non public customer…

What happened

  • On May 5, 2026, Community Bank (the “Bank”), the wholly-owned subsidiary of CB Financial Services, Inc. (the “Company”), became aware of an internal incident involving the handling of certain non public customer information using an unauthorized artificial intelligence-based software application.Form 8-K Item 1.05, CB Financial Services, Inc., filed 2026-05-11
  • The incident did not involve a disruption to the Bank's operations, customer access to accounts or services, payment systems, or core information technology infrastructure; however, due to the volume and sensitive nature of the non-public information at issue, on May 7, 2026, the Company determined the event to be material.Form 8-K Item 1.05, CB Financial Services, Inc., filed 2026-05-11
  • As of the date of this disclosure, this incident has not had, and is not expected to have, a material impact on the Company’s consolidated financial condition or results of operations. 2Form 8-K Item 1.05, CB Financial Services, Inc., filed 2026-05-11

The failure pattern

Watch the pattern: Insufficient segmentation lets a foothold spread

Related standards

CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

Building something similar?

Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

Analyze your design