You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we are using jetty 12.1.12 in pulsar 4.0, Can we get rid of jetty-bom from below modules?
@adarshhm6 I'm not aware of any current way since tiered-storage/file-system and pulsar-io/alluxio require Jetty 9.4.x
The only way to get security fixes for Jetty 9.4.x is to get commercial support and commercial releases, https://www.herodevs.com/support/nes-for-jetty. This isn't an option for Apache Pulsar OSS.
What problem do you have with the Jetty 9 dependencies? If you are concerned about the CVEs, you have the option to not use the components that ship a vulnerable Jetty 9 dependency. The core Pulsar distribution doesn't ship with Jetty 9.
It's very rare that anyone would be using tiered-storage/file-system. The same applies to pulsar-io/alluxio.
Activity
lhotari commentedon Aug 11, 2026
@adarshhm6 I'm not aware of any current way since tiered-storage/file-system and pulsar-io/alluxio require Jetty 9.4.x
The only way to get security fixes for Jetty 9.4.x is to get commercial support and commercial releases, https://www.herodevs.com/support/nes-for-jetty. This isn't an option for Apache Pulsar OSS.
What problem do you have with the Jetty 9 dependencies? If you are concerned about the CVEs, you have the option to not use the components that ship a vulnerable Jetty 9 dependency. The core Pulsar distribution doesn't ship with Jetty 9.
It's very rare that anyone would be using
tiered-storage/file-system. The same applies topulsar-io/alluxio.