Vaadin 24 Free Maintenance Has Ended — Here's what you need to know

Flow
1

Hi everyone,

As of June 16, 2026, free maintenance for Vaadin 24 has ended. We want to make sure everyone understands what this means and what your options are.

What changed: Vaadin 24 will no longer receive free security patches, browser compatibility fixes, or critical bug fixes. Your applications will continue to run — nothing breaks overnight — but newly discovered vulnerabilities and browser changes will no longer be addressed on the free track.

If you’re still on V24, you have two paths forward:

  1. Get Extended Maintenance to keep your V24 application secure and supported without being forced into an immediate upgrade. It covers security patches, browser compatibility updates, and critical bug fixes for your specific V24 minor version for up to 15 years. Enterprise plan subscribers already have access. Learn more and subscribe at vaadin.com/maintenance.
  2. Upgrade to Vaadin 25.1 for the best long-term path. For teams already on Java 21, the migration is often straightforward. If you’re planning to upgrade but need time to test and roll out, Extended Maintenance keeps you covered in the meantime.

Not sure where you stand? Book a 30-minute consultation and we’ll review your version, coverage, and options with you.

We’ve published a full post explaining the details: Vaadin 24 Free Maintenance End – What Does It Mean And What To Do?

If you have questions about your specific situation, feel free to ask in this thread.

2

Hey :slight_smile:

only one question. We want to upgrade ASAP from latest 24. Only “problem” I have identified: We deploy a war on RedHat 8 JWS6. From Redhat there are no news yet when a JWS will be available supporting Jakarta EE 11. As JWS is in the RedHat repos it makes it easy tu update it in case of patches etc, unlike a Apache Tomcat which has to be updated manually.

Is it safe to run a Vaadin 25 app in a Jakarta EE 10 Server as long as we have only the standard components we already use in current Vaadin 24 and don’t use any of the newer features?

Otherwise I need to discuss with our IT about the best way for running that, if as jar using systemd or whatever :slight_smile:

Thanks and keep up the good work!
Mojo

3

Is it safe to run a Vaadin 25 app in a Jakarta EE 10 Server as long as we have only the standard components we already use in current Vaadin 24 and don’t use any of the newer features?

While it seems like Vaadin 25 works nicely also on Jakarta EE 10 today, we’re not guaranteeing that this will remain also in the future . We might make code changes to any part of the framework at any time and might then end up using APIs that are not available in Jakarta EE 10. This is just as likely to happen for older features as for newer ones so you won’t be “safe” just by sticking to only older Vaadin features.

1 Like
4

Thanks Leif, so I will try out with the current JWS6 as it is anyway only for an interim period. Either a updated version of JWS will come soon or another technical solution will take place on the server.

At least it gives us a bit more time :slight_smile:
Mojo