Zeabur Discloses Second Data Breach in Seven Weeks

The platform's latest security failure exposed API tokens and environment variables across dedicated cloud servers.

Updated on Oct. 16, 2026 in Cybersecurity

Bold flat-color editorial illustration of a stylized server rack in navy and cream, representing an architectural infrastructure vulnerability. — Zeabur has disclosed its second data breach in seven weeks, citing a security failure in legacy infrastructure that exposed user environment variables. AI Illustration. Upload story photo >

Live Poll

Do you trust cloud platform providers to adequately protect your sensitive digital credentials and data?

Zeabur has disclosed a data breach that occurred on October 14, 2026, exposing user secrets and account information. Attackers gained read access to an internal database and compromised dedicated Google Cloud servers during a four-hour window.

Why it matters

This incident highlights recurring security vulnerabilities at Zeabur, marking the second such disclosure by the company in just seven weeks. The breach underscores the risks associated with legacy infrastructure, as the company identified a shared cluster as the origin of the intrusion.

The intrusion spanned a four-hour window, specifically between 9 a.m. and 1 p.m. ET on October 14, 2026. This unauthorized access impacted environment variables, account details, Zeabur API tokens, and keys for the zSend email service.

The players

Zeabur

A cloud platform provider that offers automated deployment and hosting for developers.

Google Cloud

A suite of cloud computing services providing infrastructure for computing, data storage, and machine learning.

The details

The breach originated in a legacy shared cluster before attackers pivoted to obtain read access to an internal database. From there, they compromised dedicated Google Cloud servers, a managed infrastructure service that Zeabur uses to host its applications. In response, the company has officially phased out the shared cluster where the security failure began.

August 27, 2026: The company experienced a prior data breach.
October 14, 2026, 9:00-13:00 ET: Attackers gained unauthorized access to internal systems.

The Tech Race

The incident demonstrates the critical challenge of securing legacy infrastructure in rapid-deployment cloud environments. It highlights the failure to properly isolate older shared clusters from sensitive production databases.

Users should treat any stored API tokens or email service keys as compromised and rotate them immediately. The incident suggests that security protocols at Zeabur remain in a state of adjustment following two breaches in under two months.

The takeaway

The repeat nature of these security failures suggests that infrastructure hardening at Zeabur is an ongoing process rather than a solved problem. Users should monitor for further security bulletins and prioritize credential rotation across all affected services.