Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-42527: 0.67% estimated exploitation activity in the next 30 days; percentile 51.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Deserialization of Untrusted Data vulnerability in Apache Camel. The default ObjectInputFilter pattern shipped with several Apache Camel components for defense-in-depth deserialization filtering ('java.;javax.;org.apache.camel.;!', or the no-'javax.' variant in the aggregation-repository components) uses a recursive 'java.' glob that admits classes whose hashCode/equals/readObject methods perform network I/O, notably java.net.URL and java.net.InetAddress. When an attacker can deliver a Java-serialized payload to an affected Camel consumer, deserialization of a HashMap (or any collection that calls hashCode on its elements) containing java.net.URL keys causes the JVM to issue DNS queries to the attacker-supplied host during the deserialization side-effect. The class-level filter check passes because the resulting object's class (HashMap) is allow-listed; the DNS query is observable on an attacker-controlled DNS server, providing an out-of-band side channel. The exposure is highest on…

Published by the source

6 Jul 2026, 09:30 UTC

Last modified by the source

26 Aug 2026, 15:12 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8h6p-jvhf-9hcr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42527

Advisory: Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure
IDs: CVE-2026-42527, GHSA-8h6p-jvhf-9hcr
Record: https://patchnext.com/advisories/cve-2026-42527 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-leveldb 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-sql 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-vertx-http 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-jms 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-sjms 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-consul 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-netty-http 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-infinispan 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-amqp 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-mina 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-cassandraql 4.21.0, 4.18.3, 4.14.8; org.apache.camel:camel-netty 4.21.0, 4.18.3, 4.14.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-leveldb: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-sql: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-vertx-http: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-jms: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-sjms: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-consul: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-netty-http: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-infinispan: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-amqp: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-mina: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-cassandraql: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3
- Maven org.apache.camel:camel-netty: affected >= 4.14.0, < 4.14.8; >= 4.18.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-leveldb: check the installed version with your package manager.
- Maven org.apache.camel:camel-sql: check the installed version with your package manager.
- Maven org.apache.camel:camel-vertx-http: check the installed version with your package manager.
- Maven org.apache.camel:camel-jms: check the installed version with your package manager.
- Maven org.apache.camel:camel-sjms: check the installed version with your package manager.
- Maven org.apache.camel:camel-consul: check the installed version with your package manager.
- Maven org.apache.camel:camel-netty-http: check the installed version with your package manager.
- Maven org.apache.camel:camel-infinispan: check the installed version with your package manager.
- Maven org.apache.camel:camel-amqp: check the installed version with your package manager.
- Maven org.apache.camel:camel-mina: check the installed version with your package manager.
- Maven org.apache.camel:camel-cassandraql: check the installed version with your package manager.
- Maven org.apache.camel:camel-netty: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-leveldb, org.apache.camel:camel-sql, org.apache.camel:camel-vertx-http, org.apache.camel:camel-jms, org.apache.camel:camel-sjms, org.apache.camel:camel-consul, org.apache.camel:camel-netty-http, org.apache.camel:camel-infinispan, org.apache.camel:camel-amqp, org.apache.camel:camel-mina, org.apache.camel:camel-cassandraql, org.apache.camel:camel-netty.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8h6p-jvhf-9hcr (GitHub-reviewed advisory GHSA-8h6p-jvhf-9hcr lists affected ranges: Maven org.apache.camel:camel-jms >=4.14.0 =4.18.0 =4.19.0 =4.14.0 =4.18.0 =4.19.0 =4.14.0 =4.18.0 =4.19.0 =4.14.0 =4.18.0 =4.19.0 =4.14.0 =4.18.0 =4.19.0…)

Commands are suggestions: review each one before running it.