The critical log4j vulnerability, the logging library of the widely used Apache web server, was worldwide in the news. As part of our services make use of Apache web servers, we therefore screened them immediately. The initial conclusion was that the vulnerability is not present in our core services. Because we didn’t enable log4j there.
Afterwards, we looked into third party frameworks that we use. There, we detected the presence of the log4j function in the Elastic Search environment. A popular open source environment for real-time indexing and search. We urgently updated this framework with a log4j patch.
We did this vulnerability sweep on top of our standard security monitoring and maintenance protocol.
A 9.2 severity PHP flaw went public on Wednesday; the first scanner reached us the…
Sprint 106 touched several parts of the platform. The AI Assistant got a new engine…
From 1 November 2026, the EU requires product identifiers on the customs declaration for online…
Retailers are taking different approaches to AI shopping agents, with some welcoming automated purchases while…
TikTok Shop continues to generate significantly more sales in the United Kingdom than in any…
Amazon unveiled a series of AI-powered tools and services to help independent sellers automate daily…