We are currently running Jenkins 2.568.3 LTS.
Our vulnerability scanning has identified vulnerabilities in the Eclipse Jetty version bundled with Jenkins and recommends upgrading to Jetty 12.1.13 or later.
We understand that Jetty is provided through Jenkins/Winstone and therefore do not intend to replace the Jetty libraries manually.
Could someone confirm whether an upgrade to Jetty 12.1.13 is currently planned or being tracked in Winstone/Jenkins?
In particular:
Is there an existing Winstone/Jenkins issue or PR tracking Jetty 12.1.13?
Which Jenkins release is expected to contain Jetty 12.1.13 or later?
Is the update expected to be included in the next Jenkins LTS release?
Is there a recommended remediation for Jenkins LTS users in the meantime?
We would prefer to remain on the Jenkins LTS release line rather than move our production controller to a weekly build.
Thanks.
I’m not aware of any vulnerability in Jetty 12.1.12 that would need remediation. Please provide the CVE identifier for the issue. I doubt that it affects Jenkins, but without the CVE identifier, there is no way to know for sure.
This was detected by Microsoft rather than Tenable.
CVE-2026-19204 — WebSocket frames with unknown opcodes and huge declared payload lengths can exhaust the JVM heap; published 7 September 2026, CVSS 8.7
High – CVSSv3 score = 7.5
CVE-2026-19203 — HTTP request smuggling via lone LF terminators in chunked request parsing; published 8 September 2026, CVSS 8.3
As far as I can tell from the NVD and Mitre pages for those issues, they are resolved in Jetty 12.1.12 and later. Jenkins 2.568.3 includes Jetty 12.1.12.
CVE-2026-12611 — HTTP/2 race condition with RST_STREAM/GOAWAY frames that blocks all threads and hangs the server; published 8 September 2026, CVSS 8.7
High – CVSSv3 score = 5.9
Tenable said they werent but i can push back as they often get things wrong