Mendix Technology B.V. Status

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: This incident has been resolved.

Monitoring: The fix for Java 11 has been released and rolled out across Mendix Cloud. Java 11 now includes the October 2026 Critical Patch Update, like Java 25, 21 and 17.

What you need to do If your app is running on Java 11, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Identified: The fix for Java 17 has been released and rolled out across Mendix Cloud. If your app is running on Java 17, please follow the redeploy instructions as listed in the original statuspage message. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

Identified: What happened On 20 October 2026, Oracle has released an October 2026 Critical Patch Update (https://blogs.oracle.com/security/october-2026-critical-patch-update-released) that includes multiple fixes for Java versions that are in use by Mendix apps.

Who is affected All customers with applications running on Mendix Cloud.

What we did We have updated the Java version for Java 25, Java 21 and Java 17. These new versions include the critical patch updates. For Java 11, we're waiting for an update from our vendors. Once these updates are available, we will update the Java versions used on Mendix Cloud.

What you need to do If your app is running on Java 17, 21 or Java 25, you should redeploy your app. You can find the Java version used for your environment on the Environment Details page (https://docs.mendix.com/developerportal/deploy/environments-details/#application-status). You can redeploy the same package that is already running on your environment, or build and deploy a new package. A restart is not enough!

We recommend doing this in your usual order, so you can check that your applications still work before updating production:

1. Test environment
2. Acceptance environment
3. Production environment

If your app is running on Java 11, you should keep an eye on this Statuspage incident. We will update this when we release new Java versions on Mendix Cloud. These updates will include instructions for the specific Java versions.

Deployment requirements To apply these security fixes, you must perform a regular deployment (non-Zero Downtime Deployment). Zero Downtime Deployment (ZDT) will not apply these security fixes, even when redeploying an existing deployment package. You do not need to create a new deployment package. You can redeploy your existing package using the regular deployment process. If you have already performed a Zero Downtime Deployment to apply these fixes, please redeploy using the regular deployment process. A regular deployment causes a short period of downtime while the application restarts, so please plan accordingly.

If you have any questions, feel free to contact support.

Resolved: A fix has been released. Newly built apps on Mendix on Kubernetes and Mendix on Azure start normally again. If an environment failed to start, deploy the app to that environment again. This builds a new image that contains the fix. Restarting the environment is not enough, because a restart reuses the faulty image. Environments that kept running are not affected and do not need any action. You can deploy as usual again. If you pull the Mendix runtime base images through your own registry mirror, sync them again before you redeploy.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We identified the root cause and prepared a fix. It is currently propagating through our release pipeline.

Investigating: We are curently investigating the issue.

Do not deploy or redeploy running environments until further notice. Restarting environments is safe. Do not downgrade the Operator, downgrading the Operator is unsupported an will not resolve the issue.

Resolved: A fix has been released. Newly built apps on Mendix on Kubernetes and Mendix on Azure start normally again. If an environment failed to start, deploy the app to that environment again. This builds a new image that contains the fix. Restarting the environment is not enough, because a restart reuses the faulty image. Environments that kept running are not affected and do not need any action. You can deploy as usual again. If you pull the Mendix runtime base images through your own registry mirror, sync them again before you redeploy.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We identified the root cause and prepared a fix. It is currently propagating through our release pipeline.

Investigating: We are curently investigating the issue.

Do not deploy or redeploy running environments until further notice. Restarting environments is safe. Do not downgrade the Operator, downgrading the Operator is unsupported an will not resolve the issue.