Skip to content
VulniPulse
High8.8Apache Software Foundation

CVE-2026-46590 and CVE-2026-40048: Deserialization of Untrusted Data vulnerability in Apache Camel PQC component

This Apache advisory covers CVE-2026-46590 and CVE-2026-40048 in Apache Camel PQC. Its rating, versions and guidance apply to the bulletin as a whole, not to each of its 2 CVEs.

Open the Apache advisory

Key facts

Bulletin rating
High, CVSS 8.8
Affected
4.18.0 through 4.18.3; 4.19.0 through 4.21.0.
Fixed in
4.21.0, 4.18.3
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessaging

Description

Deserialization of Untrusted Data vulnerability in Apache Camel PQC component. The camel-pqc component persists post-quantum key metadata (KeyMetadata) through pluggable KeyLifecycleManager implementations.

HashicorpVaultKeyLifecycleManager and AwsSecretsManagerKeyLifecycleManager read that metadata back from the configured secret backend by deserializing a Base64-wrapped value with a raw java.io.ObjectInputStream.readObject() and no ObjectInputFilter or class allow-list; the cast to KeyMetadata happens only after readObject() returns, so any readObject() side effects in a crafted object run before the type check.

The same unfiltered legacy-migration read also remained in FileBasedKeyLifecycleManager (for the stored KeyPair and KeyMetadata).

A principal who can write to the operator-controlled backend that holds these values - the HashiCorp Vault KV path, or the AWS Secrets Manager secret (requiring a Vault token or secretsmanager:PutSecretValue) - could store a crafted serialized object that is deserialized during normal key-lifecycle operations, potentially leading to code execution in the context of the application that manages the keys.

Text from the source record.

Affected versions
  • 4.18.0 through 4.18.3
  • 4.19.0 through 4.21.0.

Official advisory · high-confidence parse· fetched ·verify at source

Fix and mitigation

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to version 4.21.0, which fixes the issue.

Workarounds

  • For deployments that cannot upgrade immediately, restrict write access to the key backend so that only the application's own identity can write the camel-pqc secrets (least-privilege HashiCorp Vault policies and secretsmanager:PutSecretValue IAM), and keep the PQC key material in a backend separate from any data that less-trusted principals can write.

Apache Software Foundation advisories, July 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)