Resolved after 6 hours 26 minutes, affecting Labrador Editor, on October 21, 2026.
All affected services have now been patched and the extra security layer has been removed.
Affected components
Update timeline
- investigating Oct 21, 2026, 01:50 PM UTC
Due to a worldwide active exploit in part of the software we use in our infrastructure we have turned on an extra level of security on all CMS instances. This will require an extra user/password for all users of Labrador. This will not affect readers or external services using our front APIs, but it WILL be needed for all requests to your CMS, including CMS-APIs. We will share the required credentials to all customers, but if you have not received it yet, send an email to [email protected]
- investigating Oct 21, 2026, 01:51 PM UTC
We are continuing to investigate this issue.
- identified Oct 21, 2026, 04:07 PM UTC
We have implemented the patch and will roll it out to all customers now. When all customers have received the patch we will remove the extra layer of security.
- monitoring Oct 21, 2026, 07:21 PM UTC
All customers have been upgraded, we are rolling out removal of the extra security layer now.
- resolved Oct 21, 2026, 08:17 PM UTC
All affected services have now been patched and the extra security layer has been removed.
Your product runs on more than Labrador CMS
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services