CVE Index中文
L4 · Septic Tank Blewdata breach · credit unions · SaaScredit-union-payee-exposure

Irish credit unions confirm saved-payee data exposure at a shared provider

Irish credit unions confirm unauthorized access to saved-payee information at an external online-services provider. Exposed fields can include names, bank account details, payment references and some addresses. The number of affected people remains unknown.

Disclosed
Nov 17, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
Members and saved payees at credit unions whose online-services provider confirms exposure
data breach · credit unions · SaaS
In the wild
Yes
Credit unions confirm unauthorized access to saved-payee information.

What happened

The incident concerns a shared external provider’s online-services platform. The credit unions’ notices say the compromise did not originate in their own systems. Capital reports successful retrieval of saved-payee information after exploitation on October 2–4, with the flaw closed on October 6. The November 16 notification date is distinct from the November 17 public notice cited here.

Saved payees can be linked to the member who created them. Potential fields include the payee’s bank account name and nickname, IBAN/BIC or account number and sort code, free-form payment references, and addresses where recorded. Capital also lists internal reference codes that it says contain no identifiable personal data. Payment references may themselves contain names or other identifying information. The precise retrieved subset and affected-person total remain unknown. Capital therefore treats all its saved payees as potentially affected; this is a precautionary scope, not a confirmed count of stolen records.

Capital says members’ linked accounts, balances, transaction counts and amounts, and online-banking credentials were not accessed. Phoenix and St. Canice’s exclude passwords, PINs, card details and login credentials, and say exposed payee data cannot itself provide account access. These statements do not establish a financial-loss total.

Capital assesses the limited data as not posing a high risk of fraud, phishing or identity theft. Phoenix and St. Canice’s nevertheless recommend vigilance for financial impersonation. These are the institutions’ assessments, not a guarantee that unexpected messages are genuine. Phoenix and St. Canice’s describe a wider incident affecting approximately 50 credit unions using the supplier. That is their reported institutional scope, not an independently established list or an affected-person count. Confirmed unauthorized disclosure of financial contact information across institutions supports L4.

Crime-scene timeline

  1. Oct 2–4, 2026

    Provider flaw is exploited

    Capital Credit Union reports this exploitation window; it says the flaw was closed on October 6.

  2. Nov 16, 2026

    Provider informs credit unions

    Capital, Phoenix and St. Canice’s say they were notified on this day.

  3. Nov 17, 2026

    St. Canice’s publishes its member notice

    The exact members and payees affected are still being established.

  4. Nov 18, 2026

    Capital and Phoenix publish further scope and guidance

    Capital treats all its saved payees as potentially affected because the precise retrieved subset is unknown.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.