3 hours ago
Activiti
18 hours ago
Activiti
21 hours ago
quarkus

3.39.3

Complete changelog

  • #42976 - Quarkus REST in NATIVE - abstract resources with @Path requires impl. to be CDI beans while RESTEasy does not
  • #45257 - update guide on writing extension regarding docs generation
  • #45791 - Range response status reset when using a @ServerResponseFilter
  • #55119 - Use branch instead of version to avoid dead link on main guides
  • #55674 - context propagation not working correctly
  • #55739 - Fix race in AeshLauncherImpl causing flaky test timeouts
  • #55835 - Quarkus 3.38 in dev mode - WARNING: java.lang.foreign.Linker::downcallHandle has been called by org.aesh.terminal.tty.impl.LibC in an unnamed module
  • #55962 - Enable WebSocket traffic logging in aesh websocket tests
  • #55999 - [Docs]: Lift and Shift review of Deploying to OpenShift guide
  • #56018 - Aesh: fix flaky WebSocket tests on Semeru by closing WebSocketClient
  • #56103 - Mention the quarkus-config-doc-maven-plugin
  • #56106 - Add licenses for generic file components in SBOMs
  • #56120 - Move SSH enabled config to build time and gate all processor build steps
  • #56129 - Fix wrapWithSpan context propagation
  • #56153 - Keep the 206 status of Range responses when the JAX-RS response has been materialized
  • #56222 - Make sure the callouts follow the Asciidoc syntax
  • #56240 - Update redirect instructions for Roq
  • #56279 - Security overview guide style review (3.40)
  • #56301 - Upgrade aesh to 3.17.5 and improve AeshLauncher test framework
  • #56336 - [3.39] Server-Side Template Injection (SSTI) vulnerability in ReflectionValueResolver of the Quarkus Qute template engine
  • #56340 - Add a packaging overview guide
  • #56346 - Manage projectreactor in the bom, update to 3.8.7
  • #56348 - Update building-docs skill and docs-preview.sh for Roq migration
  • #56354 - Upgrade hibernate ORM from 7.4.5.Final to 7.4.7.Final
  • #56357 - [3.39] backport of doc improvement
  • #56359 - Check Keycloak token type on the OIDC server-less verification path
  • #56365 - [3.39] Upgrade RESTEasy to 6.2.18.Final
  • #56374 - Remove warning from PeriodicMetricReader
  • #56386 - Style and syntax violations in docs callouts
  • #56389 - Do not use attributes in guide title to work around Roq/Yupiik limitation
  • #56391 - Fix numbered callout lists in documentation examples
  • #56393 - ReactiveRedisDataSource.withConnection leaks pool permit when cancelled before connection is acquired
  • #56395 - Suppress PeriodicMetricReader exporter warnings
  • #56400 - rest-jackson: ContextResolver result cached by entity class, dropping the media type from the key
  • #56402 - rest-jackson: SecurityCustomSerialization caches its ObjectWriter in a JVM-wide static field, dropping the ObjectMapper from the key
  • #56408 - Update the logging guide for supported APIs
  • #56413 - Redis client: fix connection leaks caused by cancellation during acquisition
  • #56424 - Quarkus REST: fix native mode when abstract resource with path is extended by a subclass without paths
  • #56425 - Doc - place callout lists after source listings
  • #56429 - Typo fixes in websockets-next guides
  • #56430 - Ensure FullyFeaturedServerJacksonMessageBodyWriter uses media type properly
  • #56431 - Ensure SecurityCustomSerialization uses ContextResolver
  • #56432 - Remove orphaned callout markers with missing explanations
  • #56444 - Drop steps for discarded toc plugin in docs preview
  • #56449 - Fix remaining callout list placement issues in docs
  • #56470 - [3.39] Decouple types discovery and generation of reflection-free Jackson serializers
  • #56480 - fix: align docs-preview.sh default port to 8042
  • #56487 - Update to Avro 1.12.2, auto-trust Avro-generated classes, add properties to configure additional Avro-trusted classes
  • #56489 - SBOM component to product attribution
  • #56493 - Certificate reload skips restored certificates by comparing against startup snapshot
  • #56497 - [3.39] SBOM CPE attribution
  • #56498 - Ensure restoring certificate to original works
1 days ago
selenium

Nightly

Commits

  • 0a5e0e7: [build] Reset versions to nightly after selenium-4.49.0 release (Selenium CI Bot)
  • 60238b4: Update mirror info (Wed Sep 9 15:45:10 UTC 2026) (Selenium CI Bot)
  • 56636ca: [build] key the repository cache on its trigger files and cache the Selenium Manager binaries (Titus Fortner)
  • cec4b03: [build] retry the Bazel run once after a transient download failure (Titus Fortner)
  • e44e60b: [build] pass secrets to the release verify job so it can query Sonatype (Titus Fortner)
  • ca5effb: [rust] drop stale note that Selenium Manager cannot be built locally on Windows (Titus Fortner)
  • 135dd70: [build] do not compute test targets for a release (Titus Fortner)
  • eebe911: [build] support passing multiple targets to bazel execute (Titus Fortner)
  • abc6eec: [build] build all Java release targets in one Bazel invocation (Titus Fortner)
  • e56ba7d: [build] start the Selenium Manager release build after the CDP check instead of after the trunk lock (Titus Fortner)
1 days ago
netty

netty-4.1.138.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 : 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 : 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-http2
  • CVE-2026-XXXXX : improper header validation in io.netty:netty-codec-http2
  • 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 note

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

Full Changelog: https://github.com/netty/netty/compare/netty-4.1.137.Final...netty-4.1.138.Final

1 days ago
netty

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

New Contributors

Full Changelog: https://github.com/netty/netty/compare/netty-4.2.17.Final...netty-4.2.18.Final

1 days ago
selenium

Selenium 4.49.0

Detailed Changelogs by Component

Java     |     Python     |     DotNet     |     Ruby     |     JavaScript

What's Changed

New Contributors

Full Changelog: https://github.com/SeleniumHQ/selenium/compare/selenium-4.48.0...selenium-4.49.0

1 days ago
selenium