Skip to content
VulniPulse
Medium 2 vendors · 2 advisories

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

CVE-2026-85243 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
5.9 (Apache), 5.9 (Red Hat)
Weakness
CWE-354
Fixed releases
  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85243; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-85243?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
  • Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
  • Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)

Vendor advisories for CVE-2026-85243

Apache

1 advisory
  • Advisory severityMedium5.9

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

    CVE-2026-85243Source published Source updated

    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…

    Affected products in this advisory
    • Apache Camel Crypto
    Source-reported affected versions
    • 4.0.0 before 4.18.5
    • 4.19.0 before 4.22.1
    Source-reported fixed versions
    • 4.18.5
    • 4.22.1
    Mitigation guidance
    • 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.

Red Hat

1 advisory
  • Advisory severityMedium5.9

    Medium [CVE-2026-85243] Message tampering via missing integrity check enforcement

    CVE-2026-85243Source published Source updated

    Message tampering via missing integrity check enforcement. Red Hat rates this moderate (CVSS 5.9). Weakness: CWE-354. Affected products named by the advisory: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.

    Related products — impact not confirmed
    • Red Hat build of Apache Camel 4 for Quarkus 3
    • Red Hat build of Apache Camel for Spring Boot 4
    • Red Hat Fuse 7
    Source-reported affected versions
    • < 4.0.0
    • < 4.18.5
    • < 4.19.0
    • < 4.22.1
    Source-reported fixed versions
    • 4.23.0
    • 4.18
    • 4.18.5
    • 4.22

    1 more entries in the full advisory.

    Mitigation guidance
    No mitigation guidance extracted; consult the source.

References

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on 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.

Matching phone alertsOptional email delivery