Is Amplience down?

We are aware of the recently disclosed Broccoli2Shell vulnerability (CVE-2026-111497). Our engineering and security teams are actively investigating the potential impact on Amplience services and assessing whether any additional protective measures are required. We are treating this assessment as a priority and will provide further updates as appropriate.

We are continuing to investigate this issue.

Our engineering and security teams have completed their assessment of the Broccoli2Shell vulnerability (CVE-2026-111497). Appropriate mitigations have been implemented to address the identified risks. We consider this matter resolved and will continue to monitor for any further developments.

We’re aware of an issue where assets are not displaying in Content Hub. This also impacts users importing images into content using CMS. Our teams are actively investigating the cause. At this time, we can confirm that already published assets are not impacted. Further updates will follow as soon as we have more information.

This incident has been resolved.

**Incident Start Time** 24 September 2026, 18:23 BST **Incident End Time** 24 September 2026, 18:45 BST ‌ **Issue Summary** ‌ On 24 September 2026, users experienced an issue accessing assets within DAM and the CMS Asset Library. Whilst existing published content was not impacted, users were unable to view assets within DAM, and asset libraries appeared empty in CMS when attempted to import assets into content. ‌ **Root Cause** ‌ Our investigation identified a failure within one of the shards of our search and indexing service \(SOLR\), which is responsible for making assets discoverable within DAM and the CMS Asset Library. Recovering the affected shard restored functionality.  Further investigation identified that indexing larger text-based files contributed to increased memory consumption, which we believe caused the service failure. ‌ **Corrective Actions** * We have reviewed and updated our monitoring and alerting to improve our ability to detect and respond to potential issues. * We have identified a change to the indexing process that will reduce memory consumption. This fix is currently being prioritised for release. * We will continue monitoring indexing activity and memory consumption to assess the effectiveness of these improvements.

During a routine release of improved Workforce & Flows features, we experienced a brief interruption between 16:08 and 16:12 BST. During this period, some Flows failed to complete as expected. The issue was short-lived, and normal processing resumed once the release activity completed. The impact was limited in duration, with no ongoing service degradation identified following the release.