Yandex Cloud incident

Emergency operations in Yandex StoreDoc clusters

Minor Resolved View vendor source →

Yandex Cloud experienced a minor incident on December 27, 2025 affecting Yandex StoreDoc and ru-central1-a and 1 more component, lasting 1h 40m. The incident has been resolved; the full update timeline is below.

Started
Dec 27, 2025, 10:00 PM UTC
Resolved
Dec 27, 2025, 11:40 PM UTC
Duration
1h 40m
Detected by Pingoru
Dec 27, 2025, 10:00 PM UTC

Affected components

Yandex StoreDocru-central1-aru-central1-bru-central1-d

Update timeline

  1. investigating Dec 27, 2025, 09:58 PM UTC

    In order to prevent potential information security incidents related to vulnerability exploitation CVE-2025-14847 (MongoBleed), DBMS processes will be restarted on Yandex StoreDoc (ex MongoDB) cluster hosts with public addresses between 01:00 and 03:00 on December 28, Moscow time zone. If you find any problems, contact technical support.

  2. resolved Dec 27, 2025, 11:45 PM UTC

    The DBMS processes were restarted and the zlib compressor was disabled on all hosts of Yandex StoreDoc (ex MongoDB) clusters with public IP addresses. At the moment, all clusters are operating normally. For clients with clusters without public IP addresses, we recommend that they restart the hosts themselves at a time convenient for you to apply the latest version of the database with vulnerability fix CVE‑2025‑14847 (MongoBleed). If you have any questions, please contact technical support.