Today we are publishing the April 2026 Critical Patch Update (CPU) for OpenJFX. This coordinated release delivers security and stability fixes across the current development line and all three Long Term Support streams: OpenJFX 26.0.1, 25.0.3, 21.0.11 and 17.0.19.
As with every quarterly CPU, the focus is squarely on keeping production JavaFX applications safe and running — not on shipping new features.
Why Quarterly CPUs Matter
A UI framework is only as trustworthy as the sum of its parts: the rendering pipeline, the windowing layer, the embedded web engine, and countless smaller components that each carry their own risk surface. Keeping all of that current across four release lines, on Windows, macOS (Intel and Apple Silicon) and Linux, is the kind of sustained, unglamorous work that makes JavaFX a defensible choice for regulated and long-lived desktop deployments.
Our CPU cadence exists precisely so that the teams running JavaFX in production never have to choose between “stay on a known version” and “stay secure.” Every quarter we consolidate upstream security work, regression fixes and platform-compatibility updates into a single, well-tested release per line — so that your maintenance window is predictable and your upgrade path is boring, in the best possible way.
What’s in This Release
The bulk of the fixes in this release target the embedded web engine, bringing WebKit to version 623.1 together with the accumulated upstream fixes from WebKitGTK 2.50.4, 2.50.5 and 2.50.6. Applications that render third-party or untrusted content through WebView should treat this upgrade as mandatory.
This release also resolves a Linux windowing regression in which dead keys stopped producing composed characters, as well as a build-time failure that prevented WebKit from compiling in DebugNative on Linux and macOS.
The 25.0.3, 21.0.11 and 17.0.19 releases carry the relevant backports of these fixes, adapted to each supported line.
Get the Release
- LTS Subscribers: Production-ready binaries for JavaFX 25, 21 and 17 are available now through the usual channels.
- Community Users: SDKs for 26.0.1 can be downloaded from our website, or consumed via the Maven artifacts.
We strongly recommend that all users upgrade to the appropriate CPU release for their line at the earliest convenient maintenance window.
Running JavaFX in Production? We Can Help.
Releases like today’s are only one part of what Gluon offers the OpenJFX ecosystem. If your organization depends on JavaFX, there are two ways we can partner with you directly:
- Gluon LTS gives you guaranteed access to security patches and bug fixes for JavaFX 17, 21 and 25. It’s the most direct way to keep quarterly CPUs like this one flowing, for your team and for the wider community.
- Gluon Time & Materials puts a Gluon engineer on your specific problem — a rendering glitch, a platform-specific crash, a Swing-to-JavaFX migration, an embedded deployment. We co-lead OpenJFX; there is no faster path from symptom to root cause.
Whether you need the long-term safety net or a short, sharp engagement to unblock a release, we’re here. Get in touch and we’ll take it from there.