PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619)
Monitoring - The security updates for CVE-2026-109618 and CVE-2026-109619 have been rolled out across our hosting fleet. Our teams continue to monitor the environment.

If your site uses an end-of-life PHP version (PHP 8.1 or older), we strongly recommend moving it to PHP 8.2 or newer. Some older PHP versions no longer receive security fixes from their vendors.

To check which PHP version your site is running, see: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

If you have questions about your server, please contact our Support team.
Oct 29, 2026 - 15:40 EDT
Update - Updates are continuing to roll out across our hosting fleet

To check the PHP version currently running on your site, please refer to this help article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/
Oct 29, 2026 - 09:46 EDT
Update - We are continuing to monitor patch deployment across our hosting fleets.

To check the PHP version currently running on your site, please refer to this help article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/
Oct 28, 2026 - 10:56 EDT
Update - Patch deployment is progressing well across the affected environments. Customers on EOL PHP versions are encouraged to udpate their applications to run with supported versions of PHP
Oct 27, 2026 - 10:13 EDT
Update - Patch deployment is progressing well across the affected environments.

To check the PHP version currently running on your site, please refer to this help article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

The fixed PHP versions identified so far include:

cPanel EasyApache4
ea-php74: 7.4.33-19
ea-php80: 8.0.30-12
ea-php81: 8.1.34-5
ea-php82: 8.2.35
ea-php83: 8.3.36
ea-php84: 8.4.27
ea-php85: 8.5.12

CloudLinux EasyApache4
ea-php52: 5.2.17-27
ea-php53: 5.3.29-29
ea-php54: 5.4.45-82
ea-php55: 5.5.38-64
ea-php56: 5.6.40-25
ea-php70: 7.0.33-29
ea-php71: 7.1.33-20
ea-php72: 7.2.34-12
ea-php73: 7.3.33-15
ea-php74: 7.4.33-18
ea-php80: 8.0.30-11
ea-php81: 8.1.34-4
ea-php82: 8.2.34-2
ea-php83: 8.3.35-2
ea-php84: 8.4.26-2
ea-php85: 8.5.11-2


Plesk (v18.0.81.4)
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35
PHP 8.1 (EOL) 7.4.33 (built on 21 Oct 2026)
PHP 8.0 (EOL) 77.4.33 (built on 21 Oct 2026)
PHP 7.4 (EOL) 7.4.33 (built on 21 Oct 2026)

Windows Plesk
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35

InterWorx PHP builds

Control panel PHP

IW6 (EL6, EL7)
iworxphp72-php: 7.2.34-114

IW7 (EL7, EL8)
iworxphp72-php: 7.2.34-114

IW8 (EL8, EL9)
iworxphp82-php: 8.2.35-4

Customer PHP, iworx builds

php56: 5.6.40-47.2 (EL6, EL7)
php70: 7.0.33-47.2 (EL6, EL7)
php71: 7.1.33-34.2 (EL6, EL7)
php72: 7.2.34-29.3 (EL6, EL7)
php73: 7.3.33-22.2 (EL6, EL7)
php74: 7.4.33-29.3 (EL7)
php80: 8.0.30-19.3 (EL7)
php81: 8.1.34-5.3 (EL7)
php82: 8.2.35-1.3 (EL7)
php83: 8.3.36-1.2 (EL7)

Customer PHP, system packages (EL7)

php-system: 8.3.36-1.1
php-system-centos54: 5.4.16-48.1
php-system-remi54: 5.4.45-19.1
php-system-remi55: 5.5.38-13.1
php-system-remi56: 5.6.40-41.1
php-system-remi70: 7.0.33-42.1
php-system-remi71: 7.1.33-29.1
php-system-remi72: 7.2.34-29.1
php-system-remi73: 7.3.33-22.1
php-system-remi74: 7.4.33-31.1
php-system-remi80: 8.0.30-21.1
php-system-remi81: 8.1.34-6.1
php-system-remi82: 8.2.35-1.1

Customer PHP, Remi upstream (EL8, EL9)

php85: 8.5.12
php84: 8.4.27
php83: 8.3.36
php82: 8.2.35

PHP 8.x: 8.0.30-11, 8.0.30-12, 8.0.30-21, 8.1.34-4, 8.1.34-5, 8.1.34-6, 8.2.34-2, 8.2.35, 8.3.35-2, 8.3.36, 8.4.26-2, 8.4.27, 8.5.11-2, and 8.5.12
PHP 7.x: 7.0.33-3, 7.0.33-29, 7.1.33-3, 7.1.33-20, 7.2.34-2, 7.2.34-12, 7.3.31-2, 7.3.33-15, 7.4.33-18, 7.4.33-19, and 7.4.33-31
PHP 5.x: 5.2.17-3, 5.2.17-27, 5.3.24-2, 5.3.29-29, 5.4.14-2, 5.4.45-2, 5.4.45-82, 5.5.38-2, 5.5.38-64, 5.6.40-15, and 5.6.40-25

If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have any concerns, don't hesitate to get in touch with our Support team.
Oct 26, 2026 - 06:39 EDT
Update - The security patch deployment is progressing well across the affected environments. Our teams are continuing to work toward completing the deployment and ensuring the security of the impacted services.

We will provide further updates as more information becomes available.
Oct 25, 2026 - 08:22 EDT
Update - The Patch deployment is underway across affected environments with good progress.
We will share another update as soon as more information is available.

Thank you for your understanding and patience.
Oct 24, 2026 - 17:53 EDT
Update - Patch deployment continues across the affected hosting environments. Our Security and Engineering teams are monitoring the rollout to ensure successful deployment and maintain service stability.

We will continue to provide updates as progress is made.

Thank you for your patience.
Oct 24, 2026 - 07:38 EDT
Update - Patch deployment is ongoing across our fleet. We appreciate your continued patience.
Oct 23, 2026 - 22:25 EDT
Update - We are continuing to work on a fix for this issue.
Oct 23, 2026 - 13:54 EDT
Update - We are continuing to work on a fix for this issue.
Oct 23, 2026 - 06:26 EDT
Update - Our Security and Engineering teams continue to assess the remaining hosting environments and verify the deployment of security updates. The rollout is progressing in stages, with teams monitoring systems to help maintain service stability.
We will continue to monitor progress and share further updates as more information becomes available.
To check the PHP version currently running on your site, please refer to this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

The current patched PHP builds are:

cPanel EasyApache4
ea-php74: 7.4.33-19
ea-php80: 8.0.30-12
ea-php81: 8.1.34-5
ea-php82: 8.2.35
ea-php83: 8.3.36
ea-php84: 8.4.27
ea-php85: 8.5.12

CloudLinux EasyApache4
ea-php52: 5.2.17-27
ea-php53: 5.3.29-29
ea-php54: 5.4.45-82
ea-php55: 5.5.38-64
ea-php56: 5.6.40-25
ea-php70: 7.0.33-29
ea-php71: 7.1.33-20
ea-php72: 7.2.34-12
ea-php73: 7.3.33-15
ea-php74: 7.4.33-18
ea-php80: 8.0.30-11
ea-php81: 8.1.34-4
ea-php82: 8.2.34-2
ea-php83: 8.3.35-2
ea-php84: 8.4.26-2
ea-php85: 8.5.11-2


Plesk (v18.0.81.4)
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35
PHP 8.1 (EOL) 7.4.33 (built on 21 Oct 2026)
PHP 8.0 (EOL) 77.4.33 (built on 21 Oct 2026)
PHP 7.4 (EOL) 7.4.33 (built on 21 Oct 2026)

Windows Plesk
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35

InterWorx PHP builds

Control panel PHP

IW6 (EL6, EL7)
iworxphp72-php: 7.2.34-114

IW7 (EL7, EL8)
iworxphp72-php: 7.2.34-114

IW8 (EL8, EL9)
iworxphp82-php: 8.2.35-4

Customer PHP, iworx builds

php56: 5.6.40-47.2 (EL6, EL7)
php70: 7.0.33-47.2 (EL6, EL7)
php71: 7.1.33-34.2 (EL6, EL7)
php72: 7.2.34-29.3 (EL6, EL7)
php73: 7.3.33-22.2 (EL6, EL7)
php74: 7.4.33-29.3 (EL7)
php80: 8.0.30-19.3 (EL7)
php81: 8.1.34-5.3 (EL7)
php82: 8.2.35-1.3 (EL7)
php83: 8.3.36-1.2 (EL7)

Customer PHP, system packages (EL7)

php-system: 8.3.36-1.1
php-system-centos54: 5.4.16-48.1
php-system-remi54: 5.4.45-19.1
php-system-remi55: 5.5.38-13.1
php-system-remi56: 5.6.40-41.1
php-system-remi70: 7.0.33-42.1
php-system-remi71: 7.1.33-29.1
php-system-remi72: 7.2.34-29.1
php-system-remi73: 7.3.33-22.1
php-system-remi74: 7.4.33-31.1
php-system-remi80: 8.0.30-21.1
php-system-remi81: 8.1.34-6.1
php-system-remi82: 8.2.35-1.1

Customer PHP, Remi upstream (EL8, EL9)

php85: 8.5.12
php84: 8.4.27
php83: 8.3.36
php82: 8.2.35

PHP 8.x: 8.0.30-11, 8.0.30-12, 8.0.30-21, 8.1.34-4, 8.1.34-5, 8.1.34-6, 8.2.34-2, 8.2.35, 8.3.35-2, 8.3.36, 8.4.26-2, 8.4.27, 8.5.11-2, and 8.5.12
PHP 7.x: 7.0.33-3, 7.0.33-29, 7.1.33-3, 7.1.33-20, 7.2.34-2, 7.2.34-12, 7.3.31-2, 7.3.33-15, 7.4.33-18, 7.4.33-19, and 7.4.33-31
PHP 5.x: 5.2.17-3, 5.2.17-27, 5.3.24-2, 5.3.29-29, 5.4.14-2, 5.4.45-2, 5.4.45-82, 5.5.38-2, 5.5.38-64, 5.6.40-15, and 5.6.40-25

If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have any concerns, don't hesitate to get in touch with our Support team.
Oct 23, 2026 - 04:37 EDT
Update - Our Security and Engineering teams are continuing to deploy and verify security updates across our hosting environments. The work is progressing in stages, and teams are monitoring systems throughout the rollout to help maintain service stability.

We are continuing to assess the remaining environments and will share further updates as patching progresses. To check the PHP version currently running on your site, please follow this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

If your site is running an unsupported or end-of-life PHP version, we recommend updating your code to a supported version and switching to it as soon as possible. If you need assistance or have concerns, please contact our Support team.
Oct 22, 2026 - 15:27 EDT
Update - Our Engineering teams are actively working to deploy patched PHP builds across our hosting infrastructure.

The current patched PHP builds are:

cPanel EasyApache4
ea-php74: 7.4.33-19
ea-php80: 8.0.30-12
ea-php81: 8.1.34-5
ea-php82: 8.2.35
ea-php83: 8.3.36
ea-php84: 8.4.27
ea-php85: 8.5.12

CloudLinux EasyApache4
ea-php52: 5.2.17-27
ea-php53: 5.3.29-29
ea-php54: 5.4.45-82
ea-php55: 5.5.38-64
ea-php56: 5.6.40-25
ea-php70: 7.0.33-29
ea-php71: 7.1.33-20
ea-php72: 7.2.34-12
ea-php73: 7.3.33-15
ea-php74: 7.4.33-18
ea-php80: 8.0.30-11
ea-php81: 8.1.34-4
ea-php82: 8.2.34-2
ea-php83: 8.3.35-2
ea-php84: 8.4.26-2
ea-php85: 8.5.11-2


Plesk (v18.0.81.4)
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35
PHP 8.1 (EOL) 7.4.33 (built on 21 Oct 2026)
PHP 8.0 (EOL) 77.4.33 (built on 21 Oct 2026)
PHP 7.4 (EOL) 7.4.33 (built on 21 Oct 2026)

Windows Plesk
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35


To verify that your site is patched, please follow this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

If you are not currently patched, please try running a package update through your control panel. If your site is running an unsupported/EOL version of PHP, please update your code to work on a Supported version, and switch to that as soon as possible.

We will continue to provide status updates, and we will be emailing individuals tailored information as best we can.
Oct 22, 2026 - 10:34 EDT
Update - Our Engineering teams are actively working to deploy patched PHP builds across our hosting infrastructure.

The current patched PHP builds are:

cPanel EasyApache4
ea-php74: 7.4.33-19
ea-php80: 8.0.30-12
ea-php81: 8.1.34-5
ea-php82: 8.2.35
ea-php83: 8.3.36
ea-php84: 8.4.27
ea-php85: 8.5.12

CloudLinux EasyApache4
ea-php52: 5.2.17-27
ea-php53: 5.3.29-29
ea-php54: 5.4.45-82
ea-php55: 5.5.38-64
ea-php56: 5.6.40-25
ea-php70: 7.0.33-29
ea-php71: 7.1.33-20
ea-php72: 7.2.34-12
ea-php73: 7.3.33-15
ea-php74: 7.4.33-18
ea-php80: 8.0.30-11
ea-php81: 8.1.34-4
ea-php82: 8.2.34-2
ea-php83: 8.3.35-2
ea-php84: 8.4.26-2
ea-php85: 8.5.11-2


Plesk (v18.0.81.4)
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35
PHP 8.1 (EOL) 7.4.33 (built on 21 Oct 2026)
PHP 8.0 (EOL) 77.4.33 (built on 21 Oct 2026)
PHP 7.4 (EOL) 7.4.33 (built on 21 Oct 2026)

Windows Plesk
PHP 8.5.12
PHP 8.4.27
PHP 8.3.36
PHP 8.2.35


To verify that your site is patched, please follow this Help Article: https://www.liquidweb.com/help-docs/performance/website-optimization/how-to-use-a-phpinfo-file/

If you are not currently patched, please try running a package update through your control panel. If your site is running an unsupported/EOL version of PHP, please update your code to work on a Supported version, and switch to that as soon as possible.

We will continue to provide status updates, and we will be emailing individuals tailored information as best we can.
Oct 21, 2026 - 22:09 EDT
Update - Our Security and Engineering teams are continuing to evaluate the optimal patching strategy for our hosting environments.

Customers using cPanel/WHM can patch PHP Versions 8.5, 8.4, 8.3, 8.2, along with the backported versions 8.1, 8.0 and 7.4
by performing a cPanel update and the running a yum update.

Our infrastructure remains under heightened monitoring, and we will share further details here as soon as our deployment plan and maintenance windows are finalized.

If you need assistance or have any concerns, please contact our Support team.
Oct 21, 2026 - 13:57 EDT
Update - Our Security and Engineering teams are continuing to evaluate the optimal patching strategy for our hosting environments.

We are currently analyzing the security releases and testing deployment paths in our staging environments to ensure service stability. At this time, no patches or modifications have been rolled out to production systems.

Our infrastructure remains under heightened monitoring, and we will share further details here as soon as our deployment plan and maintenance windows are finalized.

If you need assistance or have any concerns, please contact our Support team.
Oct 21, 2026 - 11:40 EDT
Identified - We are aware of recent reports regarding two critical vulnerabilities affecting PHP, identified as CVE-2026-109618 and CVE-2026-109619.

These vulnerabilities may affect web servers running PHP 5.4 and later and could potentially allow remote code execution.

Our Security and Engineering teams are actively reviewing our hosting environments to assess potential impact. As a precautionary measure, we are implementing appropriate mitigations and working to deploy the necessary security updates across affected systems as they become available.

We are continuing to closely monitor the situation and will provide further updates as additional information becomes available.

If you need assistance or have any concerns, please contact our Support team.
Oct 21, 2026 - 09:27 EDT
eMudhra Certificate Authority Security Issue
Identified - We will be performing a security update across our infrastructure to explicitly distrust the compromised eMudhra intermediate Certificate Authorities (CAs). During this maintenance, our engineering team will update the local trust stores to align with upstream security advisories.

No downtime or reboots are required. Core services and applications will remain online throughout the maintenance.

Following this update, outgoing secure connections (HTTPS/TLS) to any external service or endpoint relying on the revoked eMudhra intermediate certificates will be rejected automatically. If your integration relies on certificates issued by the affected eMudhra intermediates, ensure your certificates have been reissued under an unaffected, trusted Certificate Authority to prevent connection failures.
Oct 28, 2026 - 18:05 EDT
Investigating - We are aware of a recently reported security issue involving compromised eMudhra Certificate Authority (CA) certificates that may be present in certificate trust stores across some environments.

At this time, we have not identified any service interruptions or confirmed customer impact related to this issue.

Our Security and Engineering teams are actively evaluating the situation and working to determine and implement the appropriate mitigation across affected environments.

Additional information regarding this issue is available from Sansec:
https://sansec.io/guides/compromised-certificate-authority

We will provide additional updates as more information becomes available and as our remediation efforts progress.

If you have any questions or concerns, please don't hesitate to contact us via live chat or by opening a support case.
Oct 27, 2026 - 11:39 EDT
Proactive Mitigations for Linux Spectre v2 (BTR) Security Disclosure
Investigating - Our security and engineering teams are actively responding to an industry-wide Linux kernel security disclosure concerning a Spectre v2 Branch Target Reuse (BTR) variant (CVE-2026-64507 / CVE-2026-64508).

We will provide updates as progress is made.

If you need assistance or have any concerns, please contact our Support team.
Oct 01, 2026 - 16:57 EDT
Uptime over the past 90 days. View historical uptime.
API (example) Operational
Management Portal (example) Operational
API Operational
DNS Operational
Cloud Dedicated Operational
Cloud VPS Hosting Operational
CPanel Operational
InterWorx Operational
Plesk Operational
Object Storage Operational
VMware Cloud Operational
VMware Private Cloud Operational
Business Email Operational
Management Portal Operational
Load Balancers Operational
Cloud Load Balancers Operational
Shared Load Balancers - DC2 Operational
Shared Load Balancers - DC3 Operational
Shared Load Balancers - DC4 Operational
Shared Load Balancers - DC5 Operational
Network Operational
LAN Network Operational
PHX Network Operational
AMS Network Operational
Data Centers Operational
DC2 - LAN Operational
DC3 - LAN Operational
DC4 - PHX Operational
EU - AMS Operational
Support Services Operational
Chat Operational
Case Operational
Phone Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Scheduled Network Maintenance – Internal Firewall Updates Nov 7, 2026 22:00-23:00 EST

Scheduled: Saturday, November 7, 2026, from 10:00 PM to 11:00 PM ET

We will perform maintenance on internal network firewalls during this window. Customer-facing services are not expected to be affected. Brief network latency or packet loss may occur during firewall failovers, so we are sharing this notice as a precaution and will monitor the work throughout the maintenance.

No action is required.
Posted on Oct 30, 2026 - 14:09 EDT

Oct 31, 2026

No incidents reported today.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

Unresolved incident: PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619).

Oct 28, 2026

Unresolved incident: eMudhra Certificate Authority Security Issue.

Oct 27, 2026

Errors with Object Storage and Block Storage
Resolved - This incident has been resolved.
Oct 27, 09:21 EDT
Monitoring - A fix has been implemented and we are monitoring the results
Oct 26, 14:52 EDT
Investigating - We are currently investigating reported issues with Cloud Object Storage and Block Storage. Our engineering team is engaged and is reviewing the system to determine the cause.
Oct 26, 14:18 EDT

Oct 26, 2026

Apache Service Disruptions
Resolved - This incident has been resolved.
Oct 26, 14:12 EDT
Monitoring - We have identified the issue and implemented a fix. Affected servers are now running and we will monitor the situation to ensure that the issue is fully resolved
Oct 21, 13:45 EDT
Investigating - We are currently investigating reports of service disruptions affecting Apache web servers. Initial findings indicate this is linked to a compatibility issue with mod_security following a recent release. Our engineering team is evaluating the impact and actively working on a resolution
Oct 21, 11:36 EDT
StyleSmuggler Vulnerability – Magento & Adobe Commerce
Resolved - This incident has been resolved.
Oct 26, 13:27 EDT
Update - Our technical teams continue to actively work through the remediation process across affected environments.
The patch rollout is progressing in batches, with teams continuing to apply the available Adobe security patch across affected Magento versions.

We are also continuing system scans and validation of patched environments to help ensure affected sites can be safely restored to a known-good state.
We will continue to keep clients informed as meaningful progress is made.

If you need assistance or have any concerns, please contact our Support team.
Sep 10, 04:15 EDT
Update - Our Engineering teams continue to make progress on containment, investigation, and remediation across affected environments.

Adobe has recently released a patch addressing the underlying vulnerability. Our technical teams are actively applying the patch across affected environments in batches. There is no specific priority or ordering for the affected Magento versions; the rollout is progressing batch by batch, with our teams continuing to apply the patch across all affected versions.

At the same time, we will continue deep-system scans and validate the patched environments to ensure safe recovery paths and restore impacted sites to a known-good state.

We will continue to share updates as additional remediation details and progress become available.

If you need assistance or have any concerns, please contact our Support team.
Sep 9, 18:52 EDT
Update - Our technical teams continue to make progress on containment, investigation, and remediation across affected environments.

Adobe has recently released a patch addressing the underlying vulnerability.
Our technical teams are actively reviewing, testing, and deploying the patch while continuing deep-system scans and validating safe recovery paths to restore impacted sites to a known-good state.

We will continue to share updates as new remediation details become available.
Please contact Support if you have any questions or require assistance in the meantime.
Sep 8, 02:24 EDT
Update - Our Security and Engineering teams remain actively engaged in the ongoing containment, investigation, and remediation efforts across affected environments.

Our teams continue to review scanning results, validate findings, and take appropriate remediation actions where potential compromise has been identified. Restoration efforts are also progressing as we work to safely return affected sites to a known-good state.

We understand the importance and urgency of this situation and appreciate your continued patience. We will provide further updates as meaningful progress is made and additional remediation details become available.

If you need assistance or have any concerns, please contact our Support team.
Sep 7, 11:06 EDT
Update - Our Security and Engineering teams continue to work on containment and remediation efforts across affected environments. Deep-system scanning remains active as we work to identify, isolate, and quarantine compromised instances.

Restoration planning is also ongoing, with our technical teams validating safe recovery paths for impacted sites. While a precise time-to-resolution is still being established, restoring full system integrity safely remains our highest priority.

We appreciate your continued patience as this work continues. We will provide another status update as soon as there are meaningful developments or milestones to share.

If you need assistance or have any concerns, please contact our Support team.
Sep 7, 02:21 EDT
Update - Our Security and Engineering teams remain actively engaged and are continuing to investigate the affected environments. Confirmed threats are being quarantined as part of our ongoing containment efforts, while findings are reviewed and validated.

We are also preparing to begin restoration work where necessary. An estimated restoration timeline is not yet available, but we will share additional details as soon as they are confirmed. This remains a high priority, and we will continue to provide updates as progress is made.
Sep 6, 17:53 EDT
Update - Our teams remain actively engaged and are continuing to investigate the Magento vulnerability and its potential impact. Security and Engineering are working closely to validate findings, expand scanning, and provide clear remediation guidance for any confirmed cases.

We understand the importance and urgency of this situation and really appreciate your patience. This remains a high priority for us, and we’re here to support you throughout the process.

We recommend continuing to monitor your environment for unusual activity or unexpected changes. If you notice anything suspicious or believe your site may have been affected, please reach out to Support.

We’ll continue to closely monitor the situation and share further updates as more information becomes available. Thank you for your patience.
Sep 6, 10:29 EDT
Update - Our security teams are actively scanning affected environments for indicators of compromise. Initial scanning has identified potential findings that are currently being reviewed and validated. We are continuing to enhance our scanning capabilities to provide additional visibility into potential compromises.

We are also reviewing affected Magento environments and developing remediation guidance for confirmed cases.

Customers may experience some impact if their storefront or applications rely heavily on GraphQL, including headless/PWA implementations.

We recommend continuing to monitor your environment for unusual activity or unexpected changes and contacting Support if you observe any issues or suspect your site may have been compromised.

Our teams will continue to monitor the situation closely and provide further updates as additional information becomes available.
Sep 6, 05:08 EDT
Update - As part of our ongoing mitigation efforts, we have implemented additional security protections across affected Magento/Adobe Commerce environments. This includes a full block on GraphQL requests to help reduce the risk of unauthorized code execution.

Customers using headless/PWA storefronts or applications that rely heavily on GraphQL may experience some impact from these protections.

At this time, there is no official vendor patch available.

We recommend continuing to monitor your site for unusual activity or unexpected changes and contacting Support if you notice any issues with your storefront or suspect your site may have been compromised. We will provide further updates once an official security patch becomes available.

Our teams are continuing to monitor the affected environments and the effectiveness of these mitigations. We will continue to assess the situation and provide additional updates as new information becomes available.
Sep 5, 19:04 EDT
Identified - We are aware of recent reports regarding a critical, unpatched zero-day vulnerability, commonly referred to as “StyleSmuggler”, affecting Magento and Adobe Commerce.

At this time, our teams are actively reviewing server environments to assess any potential impact. As a precautionary measure, our Security team is implementing the appropriate mitigations while we continue our investigation and monitor for further guidance.
We will provide further updates as more information becomes available.

If you need assistance or have any concerns, please contact our Support team .
Sep 5, 09:51 EDT

Oct 25, 2026

Oct 24, 2026

Oct 23, 2026

Oct 22, 2026

Oct 21, 2026

Patch Deployment for CVE-2026-74580 Impacting Parent Servers
Resolved - All affected parent servers and child instances are now online, and services have been restored. The incident is considered resolved.

We apologize for the inconvenience and appreciate your patience while our teams worked to restore service.
Oct 21, 07:26 EDT
Update - Our engineering team has successfully brought the affected parent servers back online.

Our engineers are actively working through restoring and verifying all child instances running on those parent servers to ensure full service functionality is restored.

We appreciate your continued patience as we work to bring all impacted systems back online.
Oct 20, 15:37 EDT
Identified - During scheduled evening maintenance, our operations team began deploying security patches to update server kernels to address the CVE-2026-74580 (vghost kernel vulnerability). Following the application of the patch and server reboots we identified a subset of our parent servers did not come up cleanly.

Our engineering and development teams are actively addressing the down server and are working to bring them back online.

Restoring affected parent servers and stabilizing services is currently our highest priority.

We sincerely apologize for the unexpected interruption. Our team is working to bring all impacted systems back online as quickly and safely as possible. Further updates will be posted here as soon as new information becomes available.
Oct 20, 09:57 EDT

Oct 20, 2026

Oct 19, 2026

No incidents reported.

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage