Skip to content
VulniPulse
Advisory severityMedium5.9Apache Software Foundation

Medium [CVE-2026-85243] Improper Validation of Integrity Check Value vulnerability in Apache Camel Crypto PGP component

This medium-severity Apache Software Foundation advisory covers CVE-2026-85243 affecting Apache Camel Crypto.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-85243 Source published Source updated

VulniPulse record published Record updated

CVE-2026-85243
Affected products & platforms
Apache Software FoundationMessaging
Open source advisory

Get an email when Apache Software Foundation publishes the next one.

VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

Summary

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.

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.

Affected versions
  • 4.0.0 before 4.18.5
  • 4.19.0 before 4.22.1

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Fixed versions
  • 4.18.5
  • 4.22.1

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Mitigation checklist

Recommended fix / 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.
  • For deployments that cannot upgrade immediately, reject messages that do not use the integrity protected packet before they reach the data format.

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

All Apache Software Foundation advisories

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.