Advisory record · GHSA-857v-xvh8-7hjc

Apache Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle managers deserialize persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (incomplete remediation of CVE-2026-40048)

CVSS 8.8 HighEPSS 0.0084 · 58th percentile

Published by the GitHub Advisory Database at 6 Jul 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.camel:camel-pqcMaven>=4.18.0, <4.18.3 || >=4.19.0, <4.21.04.18.3, 4.21.0
Identifiers
GHSA-857v-xvh8-7hjc · CVE-2026-46590
Weakness (CWE)
CWE-502
Published
6 Jul 2026
Updated
28 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Camel camel-pqc versions 4.18.0 to before 4.18.3 and 4.19.0 to before 4.21.0 are vulnerable to unsafe deserialization in the HashiCorp Vault and AWS Secrets Manager key-lifecycle managers. An attacker who can write to the configured Vault path or AWS secret could store a crafted serialized object that may lead to code execution in the application. Upgrade to camel-pqc 4.21.0, or 4.18.3 on the 4.18.x LTS stream; until then, restrict write access to the key backend to the application's own identity.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0084, the 58th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.