CVE-2026-85243

Description

A flaw was found in the Apache Camel Crypto PGP (Pretty Good Privacy) component. A remote attacker capable of intercepting or altering network traffic can tamper with encrypted messages without detection by sending legacy data packets that omit integrity protection. This issue occurs because the decryption process does not enforce integrity checks on older packet formats. Consequently, the receiving application may accept and process modified data under the assumption that it is authentic.

Statement

This vulnerability is rated as having Moderate impact for Red Hat products because tampering requires an attacker to be positioned to intercept and manipulate message traffic, and exploitation only affects services that actively ingest and decrypt PGP-formatted data. In Red Hat build of Apache Camel and JBoss Fuse environments, the Camel Crypto PGP data format is not enabled by default and requires explicit inclusion in integration routes. Although legacy encrypted packets lacking modification detection codes can be silently altered, the vulnerability does not directly expose secret keys or enable remote execution.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A5.9
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactHighN/AHigh
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Modify Application Data; Other

Integrity checks usually use a secret key that helps authenticate the data origin. Skipping integrity checking generally opens up the possibility that new data from an invalid source can be injected.

Integrity,Other

Technical Impact: Other

Data that is parsed and used may be corrupted.

Non-Repudiation,Other

Technical Impact: Hide Activities; Other

Without a checksum check, it is impossible to determine if any changes have been made to the data after it was sent.

Frequently Asked Questions

Want to get errata notifications? Sign up here.