The camel‑pqc component stores post‑quantum key metadata (KeyMetadata) in AWS Secrets Manager via the AwsSecretsManagerKeyLifecycleManager. The deserializeMetadata() method decodes the stored value from Base64 and then deserializes it with a plain java.io.ObjectInputStream.readObject() call, without an ObjectInputFilter or an explicit class allow list. Because the cast to KeyMetadata occurs only after readObject() returns, any side‑effect code in a crafted malicious object runs before the type check. An attacker who can write to the secret that holds this metadata (requiring secretsmanager:PutSecretValue on it) can inject such an object, which is then deserialized during normal key‑lifecycle operations, allowing arbitrary code execution in the JVM process that manages the keys.

The affected vendor is the Apache Software Foundation and the product is Apache Camel. The vulnerable releases are versions 4.18.0 through 4.18.2 and 4.19.0 through 4.20.x.

The CVSS score of 9.8 marks the issue as critical. The EPSS score is below 1%, indicating a low current exploitation probability, and it is not listed in the CISA KEV catalogue. Authorized write access to the specific Secrets Manager secret is required; therefore the risk exists only when untrusted principals can modify that secret. Upgrading to a patched release removes the flaw, while a temporary mitigation is to enforce least‑privilege IAM on the secret and keep the key material in a separate secret from data that can be modified by lower‑trust users.