CVE-2026-85243
Received Received - Intake

Improper Integrity Check in Apache Camel Crypto PGP

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: Apache Software Foundation

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
CVE-2026-85243
EUVD
EUVD-2026-104185

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Apache Software Foundation Apache Camel 4.0.0
Apache Software Foundation Apache Camel 4.19.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-354 The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Camel Crypto PGP component involves improper validation of integrity checks. The unmarshal() function only verified integrity for OpenPGP symmetrically encrypted integrity protected data packets. Older symmetrically encrypted data packets lack this check, making them vulnerable to tampering due to OpenPGP's CFB mode being malleable without integrity protection. The sender or an intermediary could decide whether integrity checks were applied, allowing undetected message modification during transit.

Detection Guidance

Detecting this vulnerability requires checking the version of Apache Camel being used. Commands like 'mvn dependency:tree' for Maven projects or inspecting the application's dependency files can help identify if an affected version (4.0.0 to 4.18.4 or 4.19.0 to 4.22.0) is present.

Impact Analysis

This vulnerability could allow attackers to modify messages in transit without detection. If your system processes PGP-encrypted messages using Apache Camel versions 4.0.0 to 4.18.4 or 4.19.0 to 4.22.0, sensitive data could be altered without your knowledge. Confidentiality remains intact, but integrity and authenticity of messages cannot be guaranteed.

Compliance Impact

This vulnerability may impact compliance with GDPR and HIPAA by compromising data integrity. GDPR requires ensuring data accuracy and protection during processing, while HIPAA mandates integrity controls for protected health information. Unauthorized message modification could violate these requirements, potentially leading to compliance violations and legal consequences.

Mitigation Strategies

Upgrade Apache Camel to version 4.23.0 or apply the latest patches for your LTS stream (4.18.5 for 4.18.x or 4.22.1 for 4.22.x). If immediate upgrade is not possible, configure routes to reject messages without integrity protection before they reach the data format.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85243. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart