Bump the maven-minor-updates group with 9 updates

[dependabot]

Bumps the maven-minor-updates group with 9 updates:

Package	From	To
org.slf4j:slf4j-bom	2.0.18	2.0.19
com.google.protobuf:protobuf-java	4.36.0	4.36.1
org.eclipse.jetty.ee11:jetty-ee11-servlet	12.1.12	12.1.13
org.eclipse.jetty:jetty-security	12.1.12	12.1.13
org.eclipse.jetty:jetty-util	12.1.12	12.1.13
org.eclipse.jetty:jetty-server	12.1.12	12.1.13
org.eclipse.jetty:jetty-jmx	12.1.12	12.1.13
io.netty:netty-all	4.2.17.Final	4.2.18.Final
org.apache.zookeeper:zookeeper	3.9.5	3.9.6

Updates org.slf4j:slf4j-bom from 2.0.18 to 2.0.19

Release notes

Sourced from org.slf4j:slf4j-bom's releases.

SLF4J 2.0.19

2026-09-04 - Release of SLF4J 2.0.19

• When the fluent API was used with XLogger/LoggerWrapper in the slf4j-ext module, caller location was incorrectly reported. To correct this, LoggerWrapper now delegates makeLoggingEventBuilder() to the wrapped logger so that the application caller can be correctly extracted. This issue was reported in issues/464.

• In slf4j-api/DefaultLoggingEventBuilder, a failing toString() invocation on a key-value value, including StackOverflowError, no longer aborts logging. The builder now substitutes [FAILED toString()], matching the existing behaviour of MessageFormatter for message arguments. This issue was reported in issues/448.

• The isLoggable() method in SLF4JPlatformLogger now maps System.Logger.Level.ALL and Level.OFF the same way as log(), that is ALL as TRACE and OFF as ERROR, instead of treating both as always loggable. This is a follow-up to the changes introduced in 2.0.17. See issues/430.

• Published JAR files now package each module's own LICENSE.txt under META-INF/. Previously the parent POM copied the repository-root MIT license into every module, so Apache-2.0 modules such as jcl-over-slf4j and log4j-over-slf4j shipped the wrong license text. This issue was reported in issues/465.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit f0fc3e52a16d5053039495f4f3b64d191508204f associated with the tag v_2.0.19. Release built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Commits

• f0fc3e5 prepare release 2.0.19
• 2288d0c fix issues/464. slf4j-ext/XLogger incorrect caller extraction when the fluent...
• 6ff7f77 test: pin fluent API caller method name
• 2b3f94b SLF4JPlatformLogger.isLoggable should handle Logger.ALL and Logger.OFF in a c...
• 9221f77 fix(api): guard addKeyValue value toString from fatal errors
• 027c543 fix(build): package each module's LICENSE.txt into JAR META-INF
• 6140045 start work on 2.0.19-SNAPSHOT
• See full diff in compare view

Updates com.google.protobuf:protobuf-java from 4.36.0 to 4.36.1

Commits

• See full diff in compare view

Updates org.eclipse.jetty.ee11:jetty-ee11-servlet from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-security from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-util from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-server from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-jmx from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-security from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-util from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-server from 12.1.12 to 12.1.13

Updates org.eclipse.jetty:jetty-jmx from 12.1.12 to 12.1.13

Updates io.netty:netty-all from 4.2.17.Final to 4.2.18.Final

Release notes

Sourced from io.netty:netty-all's releases.

netty-4.2.18.Final

Security fixes

• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http (SPDY)
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http (HTTP/1.1)
• CVE-2026-XXXXX : denial of service vector in io.netty:netty-codec-http2
• CVE-2026-XXXXX : improper certificate validation in io.netty:netty-handler-ssl-ocsp
• CVE-2026-XXXXX : memory leak in io.netty:netty-codec-stomp
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http3
• CVE-2026-XXXXX : denial of service vector in io.netty:netty-codec-stomp
• CVE-2026-XXXXX : parser desync/response smuggling in io.netty:netty-codec-memcache
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http3
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http3
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-http3
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-smtp
• CVE-2026-XXXXX : memory leak in io.netty:netty-codec-haproxy
• CVE-2026-XXXXX : request smuggling in io.netty:netty-codec-http (RTSP)
• CVE-2026-XXXXX : request smuggling in io.netty:netty-codec-http (HTTP/1)
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http2
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http (HTTP/1)
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http3
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http3 and in io.netty:netty-codec-http2
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http2
• CVE-2026-XXXXX : improper hostname verification in io.netty:netty-codec-classes-quic
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-redis
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http (HTTP/1.1)
• CVE-2026-XXXXX : request smuggling vector in io.netty:netty-codec-http (HTTP/1.1)
• CVE-2026-XXXXX : unbounded resource usage in io.netty:netty-codec-mqtt
• CVE-2026-XXXXX : improper CRLF neutralization in io.netty:netty-codec-smtp
• CVE-2026-XXXXX : improper certificate validation in io.netty:netty-handler-ssl-ocsp
• CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http2

Compatibility Notes

A number of security fixes have added additional validation and impose new resource usage limits, which may cause existing workloads to fail or be rejected. We recommend that you test your systems thoroughly as part of your Netty upgrade.

Two specific changes are worth calling out:

QUIC now explicitly requires X509ExtendedTrustManager when hostname verification is enabled. Previously, when configuring QUIC with an endpoint identification algorithm and an X509TrustManager, hostname verification would be silently skipped. This is now considered a misconfiguration and an exception will be thrown.

HTTP/2 header value validation is now enabled by default. HTTP/2 header name validation has always been enabled by default, with an option to disable it, but HTTP/2 header value validation has been disabled by default until now. Configuration options still exist to disable this, but validation of HTTP header names and values are now both opt-in by default rather than opt-out.

What's Changed

• Use X509ExtendedTrustManager in SSLErrorTest by @​normanmaurer in netty/netty#17221
• Update setup-testlens to v1.9.4 by @​marcphilipp in netty/netty#17223

... (truncated)

Commits

• 2521f49 [maven-release-plugin] prepare release netty-4.2.18.Final
• 6fd5327 HTTP/1 absolute-form Host mismatch is translated to HTTP/3 :authority, overri...
• c44a052 SPDY: SpdySessionHandler must limit the concurrent streams
• 374d965 HTTP: Limit the maximum number of concurrent pipelined requests
• 7e8b325 HTTP/2: Limit HPACK encoding table size
• e3ebf70 OCSP: Correctly handle that nextUpdate is optional
• 5388535 STOMP: Correctly release partial content on handler removal
• 3a80f5a WebSockets: Enforce a limit for the max pipelined requests in WebSocketServer...
• 1b6ea48 HTTP3: Correctly handle ":authority" and "host" headers
• 3630659 STOMP codec content-length long-to-int truncation causes infinite decode loop...
• Additional commits viewable in compare view

Updates org.apache.zookeeper:zookeeper from 3.9.5 to 3.9.6

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
com.google.protobuf:protobuf-java	[>= 3.a, < 4]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions