CVE-2026-42527: Deserialization of Untrusted Data vulnerability in Apache Camel. The default ObjectInputFilter pattern shippe

Q: How do I fix CVE-2026-42527?

camel: upgrade to 4.14.8, 4.18.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-42527 being exploited?

CVE-2026-42527 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-42527 affect?

CVE-2026-42527 affects camel. Severity is high (CVSS 8.1). 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.**;!*',

Q: How urgent is CVE-2026-42527?

Priority 51/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

This month

HIGH 8.1REMOTEWATCHLISTUPGRADE

CVE-2026-42527 is a high-severity flaw (CVSS 8.1) affecting camel. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-07-06
Last modified	2026-10-25

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-06 09:16 UTCPublished CVE record published
2026-10-25 15:10 UTCUpdated Record last modified

apache camel UPGRADE

Affected: >= 4.14.0 and < 4.14.8 · >= 4.18.0 and < 4.18.3 · 4.20.0

Fixed in: 4.14.8, 4.18.3

Safe to downgrade to: a release before 4.14.0

1. Check installed version

apt-cache policy camel || rpm -q camel || camel --version

2. UPGRADE to 4.14.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade camel

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade camel

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.14.0 (Debian / Ubuntu)

apt-cache madison camel sudo apt install camel=<VERSION_BEFORE_4.14.0> sudo apt-mark hold camel

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list camel sudo dnf downgrade camel-<VERSION_BEFORE_4.14.0> sudo dnf versionlock add camel

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Maven · org.apache.camel:camel-jms · FIXED · 4.14.8 · vulnerable: >= 4.14.0, < 4.14.8 · source

Set org.apache.camel:camel-jms to 4.14.8 or later in pom.xml or build.gradle, then rebuild and redeploy.

Maven · org.apache.camel:camel-sjms · FIXED · 4.14.8 · vulnerable: >= 4.14.0, < 4.14.8 · source

Set org.apache.camel:camel-sjms to 4.14.8 or later in pom.xml or build.gradle, then rebuild and redeploy.

Fedora ELN · nginx-mod-headers-more · FIXED · 0.41-1.eln159 · FEDORA-2026-31f55f396a · source

sudo dnf upgrade --advisory=FEDORA-2026-31f55f396a

Fedora 46 · erlang-hex_core · FIXED · 0.21.1-1.fc46 · FEDORA-2026-f3389199ff · source

sudo dnf upgrade --advisory=FEDORA-2026-f3389199ff

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: oscerd/CVE-2026-42527 (0 stars)

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42527?

camel: upgrade to 4.14.8, 4.18.3. Exact commands for each OS are on this page.

Is CVE-2026-42527 being exploited?

CVE-2026-42527 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42527 affect?

CVE-2026-42527 affects camel. Severity is high (CVSS 8.1). 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.**;!*',

How urgent is CVE-2026-42527?

Priority 51/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-40047 CRITICAL 9.1 UPGRADE Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') vulnerability in Apache Cam
CVE-2026-43867 CRITICAL 9.8 UPGRADE Deserialization of Untrusted Data vulnerability in Apache Camel PQC Component. The camel-pqc component persis
CVE-2026-46454 CRITICAL 9.8 UPGRADE Improper Input Validation vulnerability in Apache Camel Cometd Component. The camel-cometd component maps inb
CVE-2026-46456 CRITICAL 9.8 UPGRADE Improper Input Validation vulnerability in Apache Camel AWS2-SQS Component. The camel-aws2-sqs component map
CVE-2026-48204 CRITICAL 9.8 UPGRADE Improper Input Validation, Improper Access Control vulnerability in Apache Camel in Camel Mongodb Gridfs compo

References

← Back to latest CVEs