CVE-2026-85243

Improper Validation of Integrity Check Value vulnerability in Apache Camel Crypto PGP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. 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. 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.

• CWE-354

• https://camel.apache.org/security/CVE-2026-85243.htmlMitigation, Patch, Vendor Advisory
• https://github.com/apache/camel/pull/25848Issue Tracking, Patch
• https://github.com/apache/camel/pull/25944Issue Tracking, Patch
• https://github.com/apache/camel/pull/25946Issue Tracking, Patch
• https://issues.apache.org/jira/browse/CAMEL-24441Issue Tracking, Patch

Published

Oct 19, 2026

Last Modified

Nov 3, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-85237A vulnerability in MISP's email-based one-time password (OTP…8.1
• CVE-2026-85238MISP contains a session fixation vulnerability in the Custom…6.8
• CVE-2026-85239A vulnerability in MISP's event template handling allowed an…6.5
• CVE-2026-8524Out of bounds write in WebAudio in Google Chrome prior to 14…8.8
• CVE-2026-85241A weakness has been identified in SpecterOps BloodHound up t…6.3
• CVE-2026-85242PlaywrightCapture contains a server-side request forgery (SS…6.9
• CVE-2026-85245Exposure of Data Element to Wrong Session vulnerability in A…5.9
• CVE-2026-85246Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-85247Improper Certificate Validation vulnerability in Apache Came…5.9
• CVE-2026-85248Concurrent Execution using Shared Resource with Improper Syn…5.9
• CVE-2026-85249Improper Input Validation vulnerability in Apache Camel Tika…6.5
• CVE-2026-8525Heap buffer overflow in ANGLE in Google Chrome on Mac prior …8.3