live wire
▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer
upstreambeat.ai
releaseINTEGRATION

Apache Camel 4.23 opens a new LTS line with Java 25 support

The integration framework’s new long-term-support release spans Java 17, 21 and 25 while landing a broad set of runtime, DSL and connector fixes.

Apache Camel 4.23 LTS compared with the prior baseline and Java 17, 21, 25 support.
Side by side: what changed
By The Release Desk· Oct 15, 2026the quick take — two AI hosts go live when you do

Apache Camel 4.23.0 is now the project’s new long-term-support release, giving integration teams a fresh baseline that supports Java 17, 21 and 25. The release announcement says the release contains 1,034 features and improvements, while the full release notes enumerate the fixes and artifacts.

What changed

The LTS designation is the consequential part of this release. Camel’s release notes identify 4.23.0 as the new LTS line and list Java 17, Java 21 and Java 25 as supported runtimes. The project published Maven BOM coordinates for both Camel core and Camel Spring Boot, plus signed source archives and CycloneDX SBOMs in XML and JSON formats.

The resolved-issue list is broad rather than centered on one flagship feature. It includes fixes for duplicate or lost work in storage and database consumers, graceful shutdown behavior, YAML route serialization and validation, Camel JBang development workflows, secret refresh, OAuth2 handling, MCP control operations and several connector-specific concurrency problems.

Who it affects

Teams choosing a maintained upstream baseline for new Camel deployments now have a new LTS option. The Java 25 support boundary also matters to platform teams planning runtime standardization, while users of Camel JBang, YAML DSL, cloud-storage consumers and transactional routes have concrete fixes to assess.

This is an upstream Apache Camel release. Users of vendor-packaged Camel distributions should verify the version and support policy of their distribution rather than treating the upstream artifact as an in-place vendor update.

What to do

Review the 4.23.0 resolved-issue list against the components and runtimes in use. For a new deployment, pin the published 4.23.0 BOM and verify on the intended Java version. For an existing deployment, test route serialization, consumer retry behavior, shutdown handling and connector-specific changes before moving the LTS baseline.

sources

Filed by The Release Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk