Live threats
HighCritical Nginx Memory‑Corruption Flaws (CVE‑2026‑123007 & CVE‑2026‑113425) Allow Unauthenticated Remote Code Execution BreachOpenAI Agents Hack Hugging Face Model Repository, Exposing AI Supply‑Chain Risks Rule changeCleveland mayor's office introduces ordinance to award Flock Safety $2M no‑bid contract expansion DeadlineFrench court orders DNS resolver Quad9 to block sites, prompting its withdrawal from France CriticalSix Critical F5 BIG‑IP Flaws Enable Traffic‑Management Crash and Potential RCE BreachNorth Korean Hackers Use Deepfake Video Calls to Steal Over $400 Million in Cryptocurrency FineCNIL imposes €5 million fine for storing client passwords in clear text CriticalCritical Unauthenticated RCE in Apache Roller (CVE‑2026‑129448) Actively Exploited
Updated 03:25 UTC All intelligence →
BREACH WATCH BRIEF High 🐛 Breach

Third‑Party IT Provider Hack Exposes Payee Data of 40 Irish Credit Unions

Wellington IT, a managed‑services provider for Irish credit unions, was compromised by an automated script that exploited an authorization flaw, exposing payee details for members of about 40 unions. The breach underscores the importance of robust third‑party oversight, continuous logging, and audit‑ready evidence for control‑assurance programs.

SeverityHigh
Type🐛 Breach
ConfidenceHigh
ReportedNov 18, 2026
Financial Services & FinTech Financial services – credit unions Managed‑services provider (Wellington IT) Vulnerability Exploit
Check if you use it. This incident came through a third party or the supply chain. If the product or supplier is in your estate or your vendors', start with the questions to ask below.

What happened

Between 2 Oct and 4 Oct 2026, an attacker used a script to send ~5 million requests to Wellington IT, exploiting an authorization flaw and valid credentials to read saved payee records for roughly 40 Irish credit unions. The provider notified the unions that payee names, IBANs, BICs, account numbers, sort codes, addresses and payment references may have been accessed, while passwords and card data remained secure.

Why it matters for trust and compliance

  • The incident demonstrates a lapse in the control area of vendor oversight and continuous monitoring, a control objective that maps to many frameworks and is essential for audit readiness.
  • Enable continuous monitoring of third‑party access logs to provide defensible evidence for audits.
  • Map vendor‑risk assessments to the control objective of ‘vendor oversight and monitoring’ across frameworks.

Who is affected

Financial services – credit unions Managed‑services provider (Wellington IT)

Recommended actions

  1. Audit and tighten third‑party authentication and least‑privilege access.
  2. Implement comprehensive logging of all privileged vendor actions and retain logs for forensic analysis.
  3. Run a focused vendor risk assessment against the vendor‑oversight control objective.
  4. Provide breach notifications and phishing awareness guidance to affected members.
  5. Update incident‑response playbooks to include third‑party breach scenarios.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.