Contabo confirms unauthorized access to its systems, detected on November 14, 2026. The hosting provider says it stopped the access, reset all VNC passwords and rotated affected internal credentials. Its investigation remains ongoing.

The notice was first published November 16 at 9 p.m. CET. Contabo says operations continue as usual and promises updates on the same page daily by 2 p.m. CET. Those are the provider’s statements about containment and service availability, not a completed assessment of customer exposure.

What the reset establishes

VNC is a remote screen-and-keyboard connection used for server console access. A provider-wide password reset matters to customers who rely on that recovery route. It does not establish that an attacker opened every customer’s console or entered every hosted server.

Contabo says it blocked known access paths, brought in external incident-response specialists and added monitoring and forensic measures. It currently reports no indications that personal data was leaked.

Evidence status: provider-confirmed unauthorized access; customer impact unresolved. The notice now supplies an access window, but no affected-customer count, entry point or precise inventory of systems reached. It identifies no customer software vulnerability or fixed version to install.

Update — November 17, 2026, 10:43 a.m. EST

Contabo’s 1:45 p.m. CET update dates the unauthorized access to November 13 at 15:29 CET through November 14 at 11:28 CET. It says part of its internal infrastructure was accessible during that window. This adds a start and end time to the earlier notice, which gave only the detection date.

Customers can use that interval to focus access-log review while retaining relevant records around it. Contabo continues to report no indications of leaked personal data, with the investigation ongoing. The update does not establish whether customer servers or consoles were accessed, and its precautionary recommendations remain unchanged.

Review access without assuming a fleet-wide compromise

Contabo recommends investigating suspicious activity, reviewing credentials and permissions, changing default passwords, enabling multi-factor authentication and watching for phishing.

For customers, that supports a bounded response:

  • Review account and server access records. Look for unfamiliar logins, permission changes and administrative activity. Preserve suspicious records before making changes that could erase evidence.
  • Check credentials and authorized users. Replace default or reused passwords and remove access that is no longer needed. Enable multi-factor authentication where the service supports it.
  • Verify your console access through the normal customer portal. Previously saved VNC credentials may have changed. Avoid password-reset links in unexpected messages.
  • Follow the incident page for scope changes. A working server and unchanged application logs alone cannot settle what happened in the provider’s systems.

The notice does not call for every customer to rebuild a server or rotate every application secret. Decisions beyond its precautionary guidance should follow evidence of access and any customer-specific instructions.

Caveat: Contabo is the affected provider and the source of the containment claims. “No indications” of leaked personal data is an interim finding, not proof that customer data was untouched.