-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- ---
title: "Apache Camel Security Advisory - CVE-2026-85243"
date: 2026-10-15T10:00:00+02:00
url: /security/CVE-2026-85243.html
draft: false
type: security-advisory
cve: CVE-2026-85243
severity: MEDIUM
summary: "Camel-Crypto-PGP: integrity verification downgrade - the modification detection code was verified only when the message used the integrity protected packet, so a sender choosing the legacy packet skipped the check entirely"
description: "unmarshal() verified the modification detection code only when the message was an OpenPGP symmetrically encrypted integrity protected data packet. The older symmetrically encrypted data packet carries no such code, and OpenPGP's CFB mode is malleable without one, so a message using that packet skipped the check altogether. The packet type is chosen by whoever produced the message, which left the sender - or anyone able to rewrite the message in transit - deciding whether the integrity check applied at all. The existing integrity option governs marshalling only and had no decrypt-side counterpart, so a deployment could not require integrity protection on the messages it accepted."
mitigation: "Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A requireIntegrityProtection option, defaulting to true, now rejects a message that is not integrity protected. Note that signatureVerificationOption still defaults to optional, so a message carrying no signature is accepted; the two options together are what give a decrypted message authenticity and not only confidentiality. For deployments that cannot upgrade immediately, reject messages that do not use the integrity protected packet before they reach the data format. Routes that must interoperate with a sender still emitting the legacy packet should set requireIntegrityProtection=false after upgrading, and treat the decrypted content as unauthenticated."
credit: "This issue was discovered by Claude Security Scan Tool"
affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1."
fixed: 4.18.5, 4.22.1 and 4.23.0
- ---

The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24441 refers to the various commits that resolved the issue, and has more details.

The fix was merged on main in https://github.com/apache/camel/pull/25848 (commit 9d3108def6e8344f65a70ee86832b8f5237bc82d), backported to camel-4.22.x in https://github.com/apache/camel/pull/25944 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) and to camel-4.18.x in https://github.com/apache/camel/pull/25946 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3).

The issue is classified as CWE-354 Improper Validation of Integrity Check Value. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmrQ8yYACgkQ406fOAL/
QQAC1wf8Cy6mnbuU+un3MZzaQYNvaLOxLo/zIGk7ZUjm74DGNRiE94IEfPTvF33i
OJAGfmLiw5TmEvJfc+vJJtg6bWcaEc2DCTBn1uYrulvbm2gK+eH1G9UH2Ei9X0GE
zGXeQbls7S6d8/Mj+9q8vNpKHuKc7ev9Iglh3Wz0GwqbbawkJ7iyEBLACjVHqrSg
eb0GW2vfGiQ8WbcQeJGrh9XRcSZx/fj80zRoN/mUlTKiTtV47K5mIB4o0PHmJqIJ
NpWoREpVJU3GHzjmLqePhau8zzNAuyYPvPdSclNY8MN5hP4uo1pH0sT5os73Nc+g
NtapHgcRfv/gm7azrfm116jVt+p+2w==
=2W+9
-----END PGP SIGNATURE-----